Re: [Numpy-discussion] 1.7 blockers
On Sat, Mar 24, 2012 at 10:13 PM, Charles R Harris charlesr.har...@gmail.com wrote: Hi All, There several problems with numpy master that need to be fixed before a release can be considered. 1. Datetime on windows with mingw. Opened http://projects.scipy.org/numpy/ticket/2108 for the last datetime failures. 1. Bus error on SPARC, ticket #2076. 2. NA and real/complex views of complex arrays. Number 1 has been proved to be particularly difficult, any help or suggestions for that would be much appreciated. The current work has been going in pull request 214 https://github.com/numpy/numpy/pull/214. This isn't to say that there aren't a ton of other things that need fixing or that we can skip out on the current stack of pull requests, but I think it is impossible to consider a release while those three problems are outstanding. We've closed a number of open issues and merged some PRs, but haven't made much progress on the issues above. Especially for the NA issues I'm not sure what's going on. Is anyone working on this at the moment? If so, can he/she give an update of things to change/fix and an estimate of how long that will take? Thanks, Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.7 blockers
On Mon, Apr 16, 2012 at 3:09 PM, Ralf Gommers ralf.gomm...@googlemail.comwrote: On Sat, Mar 24, 2012 at 10:13 PM, Charles R Harris charlesr.har...@gmail.com wrote: Hi All, There several problems with numpy master that need to be fixed before a release can be considered. 1. Datetime on windows with mingw. Opened http://projects.scipy.org/numpy/ticket/2108 for the last datetime failures. 1. Bus error on SPARC, ticket #2076. 2. NA and real/complex views of complex arrays. Number 1 has been proved to be particularly difficult, any help or suggestions for that would be much appreciated. The current work has been going in pull request 214 https://github.com/numpy/numpy/pull/214. This isn't to say that there aren't a ton of other things that need fixing or that we can skip out on the current stack of pull requests, but I think it is impossible to consider a release while those three problems are outstanding. We've closed a number of open issues and merged some PRs, but haven't made much progress on the issues above. Especially for the NA issues I'm not sure what's going on. Is anyone working on this at the moment? If so, can he/she give an update of things to change/fix and an estimate of how long that will take? I think I can deal with the NA issues, just haven't got around to it. I'll try to get to it sometime in the next week. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.7 blockers
On Mon, Apr 16, 2012 at 10:09 PM, Ralf Gommers ralf.gomm...@googlemail.com wrote: On Sat, Mar 24, 2012 at 10:13 PM, Charles R Harris charlesr.har...@gmail.com wrote: Hi All, There several problems with numpy master that need to be fixed before a release can be considered. Datetime on windows with mingw. Opened http://projects.scipy.org/numpy/ticket/2108 for the last datetime failures. Bus error on SPARC, ticket #2076. NA and real/complex views of complex arrays. Number 1 has been proved to be particularly difficult, any help or suggestions for that would be much appreciated. The current work has been going in pull request 214. This isn't to say that there aren't a ton of other things that need fixing or that we can skip out on the current stack of pull requests, but I think it is impossible to consider a release while those three problems are outstanding. We've closed a number of open issues and merged some PRs, but haven't made much progress on the issues above. Especially for the NA issues I'm not sure what's going on. Is anyone working on this at the moment? If so, can he/she give an update of things to change/fix and an estimate of how long that will take? There's been some ongoing behind-the-scenes discussion of the overall NA problem, but I wouldn't try to give an estimate on the outcome. My personal opinion is that given you already added the note to the docs that masked arrays are in a kind of experimental prototype state for this release, some small inconsistencies in their behaviour shouldn't be a release blocker. The release notes already have a whole list of stuff that's unsupported in the presence of masks (Fancy indexing...UFunc.accumulate, UFunc.reduceat...where=...ndarray.argmax, ndarray.argmin...), I'm not sure why .real and .imag are blockers and they aren't :-). Maybe just make a note of them on that list? (Unless of course Chuck fixes them before the other blockers are finished, as per his email that just arrived.) -- Nathaniel ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.7 blockers
On Mon, Apr 16, 2012 at 11:29 PM, Nathaniel Smith n...@pobox.com wrote: On Mon, Apr 16, 2012 at 10:09 PM, Ralf Gommers ralf.gomm...@googlemail.com wrote: On Sat, Mar 24, 2012 at 10:13 PM, Charles R Harris charlesr.har...@gmail.com wrote: Hi All, There several problems with numpy master that need to be fixed before a release can be considered. Datetime on windows with mingw. Opened http://projects.scipy.org/numpy/ticket/2108 for the last datetime failures. Bus error on SPARC, ticket #2076. NA and real/complex views of complex arrays. Number 1 has been proved to be particularly difficult, any help or suggestions for that would be much appreciated. The current work has been going in pull request 214. This isn't to say that there aren't a ton of other things that need fixing or that we can skip out on the current stack of pull requests, but I think it is impossible to consider a release while those three problems are outstanding. We've closed a number of open issues and merged some PRs, but haven't made much progress on the issues above. Especially for the NA issues I'm not sure what's going on. Is anyone working on this at the moment? If so, can he/she give an update of things to change/fix and an estimate of how long that will take? There's been some ongoing behind-the-scenes discussion of the overall NA problem, but I wouldn't try to give an estimate on the outcome. My personal opinion is that given you already added the note to the docs that masked arrays are in a kind of experimental prototype state for this release, some small inconsistencies in their behaviour shouldn't be a release blocker. The release notes already have a whole list of stuff that's unsupported in the presence of masks (Fancy indexing...UFunc.accumulate, UFunc.reduceat...where=...ndarray.argmax, ndarray.argmin...), I'm not sure why .real and .imag are blockers and they aren't :-). Maybe just make a note of them on that list? (Unless of course Chuck fixes them before the other blockers are finished, as per his email that just arrived.) Good point. If you look at the open tickets for 1.7.0 ( http://projects.scipy.org/numpy/report/3) with a view on getting a release out soon, you could do the following: #2066 : close as fixed. #2078 : regression, should fix. #1578 : important to fix, but not a regression. Include only if fixed on time. #1755 : mark as knownfail. #2025 : document as not working as expected yet. #2047 : fix or postpone. Pearu indicated this will take him a few hours. #2076 : one of many. not a blocker, postpone. #2101 : need to do this. shouldn't cost much time. #2108 : status unclear. likely a blocker. Can someone who knows about datetime give some feedback on #2108? If that's not a blocker, a release within a couple of weeks can be considered. Although not fixing #1578 is questionable, and we need to revisit the LTS release debate... Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.7 blockers
On Mon, Mar 26, 2012 at 1:27 AM, Charles R Harris charlesr.har...@gmail.com wrote: On Sun, Mar 25, 2012 at 3:14 PM, Ralf Gommers ralf.gomm...@googlemail.com wrote: On Sat, Mar 24, 2012 at 10:13 PM, Charles R Harris charlesr.har...@gmail.com wrote: Hi All, There several problems with numpy master that need to be fixed before a release can be considered. 1. Datetime on windows with mingw. 2. Bus error on SPARC, ticket #2076. 3. NA and real/complex views of complex arrays. Number 1 has been proved to be particularly difficult, any help or suggestions for that would be much appreciated. The current work has been going in pull request 214 https://github.com/numpy/numpy/pull/214. This isn't to say that there aren't a ton of other things that need fixing or that we can skip out on the current stack of pull requests, but I think it is impossible to consider a release while those three problems are outstanding. Why do you consider (2) a blocker? Not saying it's not important, but there are eight other open tickets with segfaults. Some are more esoteric than other, but I don't see why for example #1713 and #1808 are less important than this one. #1522 provides a patch that fixes a segfault by the way, could use a review. I wasn't aware of the other segfaults, I'd like to get them all fixed... The list was meant to elicit additions. There are actually even more, I just searched for segfault to find the 8. Search for segmentation fault or bus error in Trac. I would hope these have a high priority to get fixed but, unless they're backwards compatibility issues, I don't consider them blockers. For the simple reason that then we'd never be able to ship any release. I don't know where the missed floating point errors come from, but they are somewhat dependent on the compiler doing the right thing and hardware support. I'd welcome any insight into why we get them on SPARC (underflow) and Windows (overflow). The windows buildbot doesn't seem to be updating correctly since it is still missing the combinations method that is now part of the test module. Yeah, none of them are updating, it's a pain. We'll hopefully soon be able to switch to a shiny new one. Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.7 blockers
On Sat, Mar 24, 2012 at 10:13 PM, Charles R Harris charlesr.har...@gmail.com wrote: Hi All, There several problems with numpy master that need to be fixed before a release can be considered. 1. Datetime on windows with mingw. 2. Bus error on SPARC, ticket #2076. 3. NA and real/complex views of complex arrays. Number 1 has been proved to be particularly difficult, any help or suggestions for that would be much appreciated. The current work has been going in pull request 214 https://github.com/numpy/numpy/pull/214. This isn't to say that there aren't a ton of other things that need fixing or that we can skip out on the current stack of pull requests, but I think it is impossible to consider a release while those three problems are outstanding. There's one more ticket that hasn't been looked at AFAIK and that has been keeping the buildbots (except the Linux one) on red: http://projects.scipy.org/numpy/ticket/1755 (floating point errors). The other tickets have been looked at and either have PRs already or should be fixable with not too much effort. Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.7 blockers
On Sun, Mar 25, 2012 at 10:33 AM, Ralf Gommers ralf.gomm...@googlemail.comwrote: On Sat, Mar 24, 2012 at 10:13 PM, Charles R Harris charlesr.har...@gmail.com wrote: Hi All, There several problems with numpy master that need to be fixed before a release can be considered. 1. Datetime on windows with mingw. 2. Bus error on SPARC, ticket #2076. 3. NA and real/complex views of complex arrays. Number 1 has been proved to be particularly difficult, any help or suggestions for that would be much appreciated. The current work has been going in pull request 214 https://github.com/numpy/numpy/pull/214. This isn't to say that there aren't a ton of other things that need fixing or that we can skip out on the current stack of pull requests, but I think it is impossible to consider a release while those three problems are outstanding. There's one more ticket that hasn't been looked at AFAIK and that has been keeping the buildbots (except the Linux one) on red: http://projects.scipy.org/numpy/ticket/1755 (floating point errors). I don't know what to do about that one.There may be some compiler flags that would help. The other tickets have been looked at and either have PRs already or should be fixable with not too much effort. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.7 blockers
On Sun, Mar 25, 2012 at 6:48 PM, Charles R Harris charlesr.har...@gmail.com
wrote:
On Sun, Mar 25, 2012 at 10:33 AM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Sat, Mar 24, 2012 at 10:13 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
Hi All,
There several problems with numpy master that need to be fixed before a
release can be considered.
1. Datetime on windows with mingw.
2. Bus error on SPARC, ticket #2076.
3. NA and real/complex views of complex arrays.
Number 1 has been proved to be particularly difficult, any help or
suggestions for that would be much appreciated. The current work has been
going in pull request 214 https://github.com/numpy/numpy/pull/214.
This isn't to say that there aren't a ton of other things that need
fixing or that we can skip out on the current stack of pull requests, but I
think it is impossible to consider a release while those three problems are
outstanding.
There's one more ticket that hasn't been looked at AFAIK and that has
been keeping the buildbots (except the Linux one) on red:
http://projects.scipy.org/numpy/ticket/1755 (floating point errors).
I don't know what to do about that one.There may be some compiler flags
that would help.
Why do you think this isn't a problem with the implementation? I haven't
tried to look at this in detail, but Python itself does manage to produce a
warning:
2.0**2048
Traceback (most recent call last):
File stdin, line 1, in module
OverflowError: (34, 'Result too large')
import numpy as np
np.power(2.0, 2048)
inf
np.geterr()
{'over': 'warn', 'divide': 'warn', 'invalid': 'warn', 'under': 'ignore'}
Ralf
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.7 blockers
On Sat, Mar 24, 2012 at 10:13 PM, Charles R Harris charlesr.har...@gmail.com wrote: Hi All, There several problems with numpy master that need to be fixed before a release can be considered. 1. Datetime on windows with mingw. 2. Bus error on SPARC, ticket #2076. 3. NA and real/complex views of complex arrays. Number 1 has been proved to be particularly difficult, any help or suggestions for that would be much appreciated. The current work has been going in pull request 214 https://github.com/numpy/numpy/pull/214. This isn't to say that there aren't a ton of other things that need fixing or that we can skip out on the current stack of pull requests, but I think it is impossible to consider a release while those three problems are outstanding. Why do you consider (2) a blocker? Not saying it's not important, but there are eight other open tickets with segfaults. Some are more esoteric than other, but I don't see why for example #1713 and #1808 are less important than this one. #1522 provides a patch that fixes a segfault by the way, could use a review. Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.7 blockers
On Sun, Mar 25, 2012 at 3:14 PM, Ralf Gommers ralf.gomm...@googlemail.comwrote: On Sat, Mar 24, 2012 at 10:13 PM, Charles R Harris charlesr.har...@gmail.com wrote: Hi All, There several problems with numpy master that need to be fixed before a release can be considered. 1. Datetime on windows with mingw. 2. Bus error on SPARC, ticket #2076. 3. NA and real/complex views of complex arrays. Number 1 has been proved to be particularly difficult, any help or suggestions for that would be much appreciated. The current work has been going in pull request 214 https://github.com/numpy/numpy/pull/214. This isn't to say that there aren't a ton of other things that need fixing or that we can skip out on the current stack of pull requests, but I think it is impossible to consider a release while those three problems are outstanding. Why do you consider (2) a blocker? Not saying it's not important, but there are eight other open tickets with segfaults. Some are more esoteric than other, but I don't see why for example #1713 and #1808 are less important than this one. #1522 provides a patch that fixes a segfault by the way, could use a review. I wasn't aware of the other segfaults, I'd like to get them all fixed... The list was meant to elicit additions. I don't know where the missed floating point errors come from, but they are somewhat dependent on the compiler doing the right thing and hardware support. I'd welcome any insight into why we get them on SPARC (underflow) and Windows (overflow). The windows buildbot doesn't seem to be updating correctly since it is still missing the combinations method that is now part of the test module. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
