Re: [Numpy-discussion] status for 1.6.0
On Fri, Apr 22, 2011 at 11:54 PM, Mark Wiebe mwwi...@gmail.com wrote: On Sun, Apr 17, 2011 at 8:55 AM, Ralf Gommers ralf.gomm...@googlemail.com wrote: Hi, The list of open issues for 1.6.0 is down to a handful: - f2py segfault on Ubuntu reported by David (David, did you get any further with this?) - #1801: test_noncentral_f failure on win64 - #1798: type promotion regression (needs review, https://github.com/numpy/numpy/pull/73) I've pushed this change, anyone interested should review the tests for this to verify that it accords with their intuition: https://github.com/numpy/numpy/blob/maintenance%2F1.6.x/numpy/core/tests/test_numeric.py#L372 - API docs for new parameters to ufuncs (full list: 'casting', 'out', 'order', 'subok', 'dtype'), Done. Great, thanks. - API docs, some docstrings and update of NEP for datetime I'm planning to release the first release candidate next weekend if these are solved. As far as I know no one is working on the doc issues right now. It would be great if someone could step up and do this. There's a new ticket #1805 which should get fixed for the RC too. Charles already attached a patch to #1805, it would be great if you could review that. If the fix is correct we're good to go. Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] status for 1.6.0
On Sat, Apr 23, 2011 at 12:45 PM, Ralf Gommers ralf.gomm...@googlemail.comwrote: On Fri, Apr 22, 2011 at 11:54 PM, Mark Wiebe mwwi...@gmail.com wrote: On Sun, Apr 17, 2011 at 8:55 AM, Ralf Gommers ralf.gomm...@googlemail.com wrote: Hi, The list of open issues for 1.6.0 is down to a handful: - f2py segfault on Ubuntu reported by David (David, did you get any further with this?) - #1801: test_noncentral_f failure on win64 - #1798: type promotion regression (needs review, https://github.com/numpy/numpy/pull/73) I've pushed this change, anyone interested should review the tests for this to verify that it accords with their intuition: https://github.com/numpy/numpy/blob/maintenance%2F1.6.x/numpy/core/tests/test_numeric.py#L372 - API docs for new parameters to ufuncs (full list: 'casting', 'out', 'order', 'subok', 'dtype'), Done. Great, thanks. - API docs, some docstrings and update of NEP for datetime I'm planning to release the first release candidate next weekend if these are solved. As far as I know no one is working on the doc issues right now. It would be great if someone could step up and do this. There's a new ticket #1805 which should get fixed for the RC too. Charles already attached a patch to #1805, it would be great if you could review that. If the fix is correct we're good to go. Oh, that just makes numpy run. It doesn't run correctly, though, there are lots of failing tests. The patch is a work in progress and is up for review and tinkering. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] status for 1.6.0
On Thu, Apr 21, 2011 at 3:37 AM, Christoph Gohlke cgoh...@uci.edu wrote: On 4/20/2011 1:55 PM, Ralf Gommers wrote: On Mon, Apr 18, 2011 at 2:36 AM, Christoph Gohlkecgoh...@uci.edu wrote: On 4/17/2011 8:55 AM, Ralf Gommers wrote: Hi, The list of open issues for 1.6.0 is down to a handful: - f2py segfault on Ubuntu reported by David (David, did you get any further with this?) - #1801: test_noncentral_f failure on win64 - #1798: type promotion regression (needs review, https://github.com/numpy/numpy/pull/73) - API docs for new parameters to ufuncs (full list: 'casting', 'out', 'order', 'subok', 'dtype'), - API docs, some docstrings and update of NEP for datetime I'm planning to release the first release candidate next weekend if these are solved. As far as I know no one is working on the doc issues right now. It would be great if someone could step up and do this. Thanks, Ralf Hi Ralf, I submitted a patch for issue #1801. All tests now pass on win-amd64-py3.2 with numpy 1.6.x from git. Great, thanks. Would it be possible to get the attached patch for scipy ticket #678 http://projects.scipy.org/scipy/ticket/678 into numpy 1.6? The fix/workaround for the scipy ODR failures is to change the ifort optimization flag from /O3 to /O1. Several other people already ran into this, so it would probably still good to change this for 1.6.0. This change is part of a proposed patch: http://projects.scipy.org/numpy/ticket/1378. Do any of the other changes there look relevant too? Ralf The changes for the Intel Visual Fortran Compiler looks OK. '/Qip' is the default option, and '/Qipo','/Qipo_obj' have already been removed some time ago. I have not used older Intel Fortran compilers but the '-xHOST' switch does not seem apt. Thanks for checking, should be fixed now. Cheers, Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] status for 1.6.0
On Sun, Apr 17, 2011 at 8:55 AM, Ralf Gommers ralf.gomm...@googlemail.comwrote: Hi, The list of open issues for 1.6.0 is down to a handful: - f2py segfault on Ubuntu reported by David (David, did you get any further with this?) - #1801: test_noncentral_f failure on win64 - #1798: type promotion regression (needs review, https://github.com/numpy/numpy/pull/73) I've pushed this change, anyone interested should review the tests for this to verify that it accords with their intuition: https://github.com/numpy/numpy/blob/maintenance%2F1.6.x/numpy/core/tests/test_numeric.py#L372 - API docs for new parameters to ufuncs (full list: 'casting', 'out', 'order', 'subok', 'dtype'), Done. - API docs, some docstrings and update of NEP for datetime I'm planning to release the first release candidate next weekend if these are solved. As far as I know no one is working on the doc issues right now. It would be great if someone could step up and do this. There's a new ticket #1805 which should get fixed for the RC too. -Mark ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] status for 1.6.0
On Tue, Apr 19, 2011 at 8:54 AM, David Cournapeau courn...@gmail.com wrote: On Mon, Apr 18, 2011 at 1:47 PM, David Cournapeau courn...@gmail.com wrote: On Mon, Apr 18, 2011 at 12:55 AM, Ralf Gommers ralf.gomm...@googlemail.com wrote: Hi, The list of open issues for 1.6.0 is down to a handful: - f2py segfault on Ubuntu reported by David (David, did you get any further with this?) I could reproduce on another machine (MAC OS X, different hardware), I will take a look at it tonight. Ok, so the problem appears only when run through nosetests for a in-place build of numpy. I think it is fair to say it is a bug somewhere in nosetests or some weird import-related corner cases that we don't care about. If I run the same failing test for a normal install, I don't get the issue. Okay, that for checking. That can be ignored then. Cheers, Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] status for 1.6.0
On Mon, Apr 18, 2011 at 2:36 AM, Christoph Gohlke cgoh...@uci.edu wrote: On 4/17/2011 8:55 AM, Ralf Gommers wrote: Hi, The list of open issues for 1.6.0 is down to a handful: - f2py segfault on Ubuntu reported by David (David, did you get any further with this?) - #1801: test_noncentral_f failure on win64 - #1798: type promotion regression (needs review, https://github.com/numpy/numpy/pull/73) - API docs for new parameters to ufuncs (full list: 'casting', 'out', 'order', 'subok', 'dtype'), - API docs, some docstrings and update of NEP for datetime I'm planning to release the first release candidate next weekend if these are solved. As far as I know no one is working on the doc issues right now. It would be great if someone could step up and do this. Thanks, Ralf Hi Ralf, I submitted a patch for issue #1801. All tests now pass on win-amd64-py3.2 with numpy 1.6.x from git. Great, thanks. Would it be possible to get the attached patch for scipy ticket #678 http://projects.scipy.org/scipy/ticket/678 into numpy 1.6? The fix/workaround for the scipy ODR failures is to change the ifort optimization flag from /O3 to /O1. Several other people already ran into this, so it would probably still good to change this for 1.6.0. This change is part of a proposed patch: http://projects.scipy.org/numpy/ticket/1378. Do any of the other changes there look relevant too? Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] status for 1.6.0
On 4/20/2011 1:55 PM, Ralf Gommers wrote: On Mon, Apr 18, 2011 at 2:36 AM, Christoph Gohlkecgoh...@uci.edu wrote: On 4/17/2011 8:55 AM, Ralf Gommers wrote: Hi, The list of open issues for 1.6.0 is down to a handful: - f2py segfault on Ubuntu reported by David (David, did you get any further with this?) - #1801: test_noncentral_f failure on win64 - #1798: type promotion regression (needs review, https://github.com/numpy/numpy/pull/73) - API docs for new parameters to ufuncs (full list: 'casting', 'out', 'order', 'subok', 'dtype'), - API docs, some docstrings and update of NEP for datetime I'm planning to release the first release candidate next weekend if these are solved. As far as I know no one is working on the doc issues right now. It would be great if someone could step up and do this. Thanks, Ralf Hi Ralf, I submitted a patch for issue #1801. All tests now pass on win-amd64-py3.2 with numpy 1.6.x from git. Great, thanks. Would it be possible to get the attached patch for scipy ticket #678 http://projects.scipy.org/scipy/ticket/678 into numpy 1.6? The fix/workaround for the scipy ODR failures is to change the ifort optimization flag from /O3 to /O1. Several other people already ran into this, so it would probably still good to change this for 1.6.0. This change is part of a proposed patch: http://projects.scipy.org/numpy/ticket/1378. Do any of the other changes there look relevant too? Ralf The changes for the Intel Visual Fortran Compiler looks OK. '/Qip' is the default option, and '/Qipo','/Qipo_obj' have already been removed some time ago. I have not used older Intel Fortran compilers but the '-xHOST' switch does not seem apt. Christoph ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] status for 1.6.0
On Mon, Apr 18, 2011 at 1:47 PM, David Cournapeau courn...@gmail.com wrote: On Mon, Apr 18, 2011 at 12:55 AM, Ralf Gommers ralf.gomm...@googlemail.com wrote: Hi, The list of open issues for 1.6.0 is down to a handful: - f2py segfault on Ubuntu reported by David (David, did you get any further with this?) I could reproduce on another machine (MAC OS X, different hardware), I will take a look at it tonight. Ok, so the problem appears only when run through nosetests for a in-place build of numpy. I think it is fair to say it is a bug somewhere in nosetests or some weird import-related corner cases that we don't care about. If I run the same failing test for a normal install, I don't get the issue. cheers, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] status for 1.6.0
I think I just found a reference leak in the reduction ufunc code that was exercised by some of the matplotlib regression tests. You may want to look at this before cutting a release: https://github.com/numpy/numpy/pull/76 Cheers, Mike On 04/17/2011 11:55 AM, Ralf Gommers wrote: Hi, The list of open issues for 1.6.0 is down to a handful: - f2py segfault on Ubuntu reported by David (David, did you get any further with this?) - #1801: test_noncentral_f failure on win64 - #1798: type promotion regression (needs review, https://github.com/numpy/numpy/pull/73) - API docs for new parameters to ufuncs (full list: 'casting', 'out', 'order', 'subok', 'dtype'), - API docs, some docstrings and update of NEP for datetime I'm planning to release the first release candidate next weekend if these are solved. As far as I know no one is working on the doc issues right now. It would be great if someone could step up and do this. Thanks, Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion -- Michael Droettboom Science Software Branch Space Telescope Science Institute Baltimore, Maryland, USA ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] status for 1.6.0
On 4/17/2011 8:55 AM, Ralf Gommers wrote: Hi, The list of open issues for 1.6.0 is down to a handful: - f2py segfault on Ubuntu reported by David (David, did you get any further with this?) - #1801: test_noncentral_f failure on win64 - #1798: type promotion regression (needs review, https://github.com/numpy/numpy/pull/73) - API docs for new parameters to ufuncs (full list: 'casting', 'out', 'order', 'subok', 'dtype'), - API docs, some docstrings and update of NEP for datetime I'm planning to release the first release candidate next weekend if these are solved. As far as I know no one is working on the doc issues right now. It would be great if someone could step up and do this. Thanks, Ralf Hi Ralf, I submitted a patch for issue #1801. All tests now pass on win-amd64-py3.2 with numpy 1.6.x from git. Would it be possible to get the attached patch for scipy ticket #678 http://projects.scipy.org/scipy/ticket/678 into numpy 1.6? The fix/workaround for the scipy ODR failures is to change the ifort optimization flag from /O3 to /O1. Christoph diff --git a/numpy/distutils/fcompiler/intel.py b/numpy/distutils/fcompiler/intel.py index b593a91..b2ea124 100644 --- a/numpy/distutils/fcompiler/intel.py +++ b/numpy/distutils/fcompiler/intel.py @@ -201,7 +201,7 @@ class IntelVisualFCompiler(BaseIntelFCompiler): return ['/4Yb','/d2'] def get_flags_opt(self): -return ['/O3','/Qip'] +return ['/O1','/Qip'] def get_flags_arch(self): opt = [] ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] status for 1.6.0
On Mon, Apr 18, 2011 at 12:55 AM, Ralf Gommers ralf.gomm...@googlemail.com wrote: Hi, The list of open issues for 1.6.0 is down to a handful: - f2py segfault on Ubuntu reported by David (David, did you get any further with this?) I could reproduce on another machine (MAC OS X, different hardware), I will take a look at it tonight. cheers, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
