I think we should try to get a quick bug fix version out by the end of the month. What do others think?
Chuck
2008/7/8 Charles R Harris charlesr.harris@gmail.com:
I think we should try to get a quick bug fix version out by the end of the month. What do others think?
That was the plan. We wanted a release before the conference -- early enough so that Enthought could push out an EPD release. We'd also like to include the latest docstrings to benefit the tutorials.
Cheers Stéfan
2008/7/8 Stéfan van der Walt stefan@sun.ac.za:
2008/7/8 Charles R Harris charlesr.harris@gmail.com:
I think we should try to get a quick bug fix version out by the end of the month. What do others think?
That was the plan. We wanted a release before the conference -- early enough so that Enthought could push out an EPD release. We'd also like to include the latest docstrings to benefit the tutorials.
Just to be clear, I don't think Enthought made any commitment to make an EPD release. It is more of a wish-list item, since so many people depend on the EPD for a fully-working tool-suite. We certainly need to get a release out with the latest docstrings, though.
Regards Stéfan
On Tue, Jul 8, 2008 at 10:19 AM, Stéfan van der Walt stefan@sun.ac.za wrote:
2008/7/8 Charles R Harris charlesr.harris@gmail.com:
I think we should try to get a quick bug fix version out by the end of
the
month. What do others think?
That was the plan. We wanted a release before the conference -- early enough so that Enthought could push out an EPD release. We'd also like to include the latest docstrings to benefit the tutorials.
So what is the schedule? I have 4 bugs to fix and will get to them this weekend. Should we put together a bug action list?
Chuck
On Tue, Jul 8, 2008 at 9:23 AM, Charles R Harris charlesr.harris@gmail.com wrote:
So what is the schedule? I have 4 bugs to fix and will get to them this weekend. Should we put together a bug action list?
Thanks for getting this conversation going. I have been meaning to send an email for some time now. I would like to get the 1.1.1 release out on 7/31/08, which gives us three weeks. I want to get this out soon because I would like to stick to the original plan to get the 1.2.0 release out on 8/31/2008. I will send an email about 1.2 out next, so if you want to comment on 1.2 please respond to that email.
Here is a schedule for 1.1.1: - 7/20/08 tag the 1.1.1rc1 release and prepare packages - 7/27/08 tag the 1.1.1 release and prepare packages - 7/31/08 announce release Of course, this is assuming that there are no issues with the rc. This release should include only bug-fixes and possible improved documentation. Also, as a reminder, the trunk is for 1.2 development; so please remember that 1.1.1 will be tagged off the 1.1.x branch: svn co http://svn.scipy.org/svn/numpy/branches/1.1.x numpy-1.1.x
Please use the NumPy 1.1.1 milestone if you want to create a bug action list: http://scipy.org/scipy/numpy/milestone/1.1.1
Thanks,
The NumPy 1.1.1 release date (7/31/08) is rapidly approaching and we need everyone's help. Chuck Harris has volunteered to take the lead on coordinating this release.
As a reminder here is the schedule for 1.1.1: - 7/20/08 tag the 1.1.1rc1 release and prepare packages - 7/27/08 tag the 1.1.1 release and prepare packages - 7/31/08 announce release This release should include only bug-fixes and improved documentation. We need to follow this schedule as closely as possible because we will need to start focusing on the upcoming NumPy 1.2.0 release as soon as 1.1.1 is released. As a reminder, the trunk is for 1.2.0 development; 1.1.1 will be tagged off the 1.1.x branch: svn co http://svn.scipy.org/svn/numpy/branches/1.1.x numpy-1.1.x
If you have any fixes that you haven't back-ported yet, please do so ASAP. According to our release schedule we will be tagging the release candidate for 1.1.1 next Sunday (7/20). We will be asking for wide-spread testing of the release candidate during the week of the 20th.
If you want to open a ticket specifically for this bug-fix release, please use the NumPy 1.1.1 milestone: http://scipy.org/scipy/numpy/milestone/1.1.1
Thanks,
-- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/
Hi, I haven't checked out a recent numpy (( >>> N.__version__ '1.0.3.1')) But could someone please check if the division has been changed from '/' to '//' in these places:
C:\Priithon_25_win\numpy\core\numerictypes.py:142: DeprecationWarning: classic int division bytes = bits / 8 C:\Priithon_25_win\numpy\core\numerictypes.py:182: DeprecationWarning: classic int division na_name = '%s%d' % (base.capitalize(), bit/2) C:\Priithon_25_win\numpy\core\numerictypes.py:212: DeprecationWarning: classic int division charname = 'i%d' % (bits/8,) C:\Priithon_25_win\numpy\core\numerictypes.py:213: DeprecationWarning: classic int division ucharname = 'u%d' % (bits/8,) C:\Priithon_25_win\numpy\core\numerictypes.py:409: DeprecationWarning: classic int division nbytes[obj] = val[2] / 8
I found these by starting python using the -Qwarn option.
Thanks, Sebastian Haase
On Tue, Jul 8, 2008 at 5:28 PM, Charles R Harris charlesr.harris@gmail.com wrote:
I think we should try to get a quick bug fix version out by the end of the month. What do others think?
Chuck
On Tue, Jul 8, 2008 at 6:21 PM, Sebastian Haase haase@msg.ucsf.edu wrote:
Hi, I haven't checked out a recent numpy (( >>> N.__version__ '1.0.3.1')) But could someone please check if the division has been changed from '/' to '//' in these places:
C:\Priithon_25_win\numpy\core\numerictypes.py:142: DeprecationWarning: classic int division bytes = bits / 8 C:\Priithon_25_win\numpy\core\numerictypes.py:182: DeprecationWarning: classic int division na_name = '%s%d' % (base.capitalize(), bit/2) C:\Priithon_25_win\numpy\core\numerictypes.py:212: DeprecationWarning: classic int division charname = 'i%d' % (bits/8,) C:\Priithon_25_win\numpy\core\numerictypes.py:213: DeprecationWarning: classic int division ucharname = 'u%d' % (bits/8,) C:\Priithon_25_win\numpy\core\numerictypes.py:409: DeprecationWarning: classic int division nbytes[obj] = val[2] / 8
I don't believe we have made any changes to '/'. It is going to be tricky making the transition to 3.0, a lot of code is going to break, and we haven't started down that path. Maybe next summer...
Chuck
On Mon, Jul 14, 2008 at 7:50 AM, Charles R Harris charlesr.harris@gmail.com wrote: `>
On Tue, Jul 8, 2008 at 6:21 PM, Sebastian Haase haase@msg.ucsf.edu wrote:
Hi, I haven't checked out a recent numpy (( >>> N.__version__ '1.0.3.1')) But could someone please check if the division has been changed from '/' to '//' in these places:
C:\Priithon_25_win\numpy\core\numerictypes.py:142: DeprecationWarning: classic int division bytes = bits / 8 C:\Priithon_25_win\numpy\core\numerictypes.py:182: DeprecationWarning: classic int division na_name = '%s%d' % (base.capitalize(), bit/2) C:\Priithon_25_win\numpy\core\numerictypes.py:212: DeprecationWarning: classic int division charname = 'i%d' % (bits/8,) C:\Priithon_25_win\numpy\core\numerictypes.py:213: DeprecationWarning: classic int division ucharname = 'u%d' % (bits/8,) C:\Priithon_25_win\numpy\core\numerictypes.py:409: DeprecationWarning: classic int division nbytes[obj] = val[2] / 8
I don't believe we have made any changes to '/'. It is going to be tricky making the transition to 3.0, a lot of code is going to break, and we haven't started down that path. Maybe next summer...
Chuck
Hi, thanks for the reply. Could you maybe please check in these changes, and replace the '/' with '//' at those places !?
The '//' operator is supported by Python 2.4 (if not before).
For a "matlab / IDL - like" interactive environment I'm using numpy already for some 5+ month with the -Qnew option. And everything seems to work smoothly - so those minimal changes would advance a small step further towards the already started "true division" support.
Thanks, Sebastian Haase
The NumPy 1.1.1 release date (7/31/08) is rapidly approaching and we need everyone's help. Chuck Harris has volunteered to take the lead on coordinating this release.
As a reminder here is the schedule for 1.1.1: - 7/20/08 tag the 1.1.1rc1 release and prepare packages - 7/27/08 tag the 1.1.1 release and prepare packages - 7/31/08 announce release This release should include only bug-fixes and improved documentation. We need to follow this schedule as closely as possible because we will need to start focusing on the upcoming NumPy 1.2.0 release as soon as 1.1.1 is released. As a reminder, the trunk is for 1.2.0 development; 1.1.1 will be tagged off the 1.1.x branch: svn co http://svn.scipy.org/svn/numpy/branches/1.1.x numpy-1.1.x
If you have any fixes that you haven't back-ported yet, please do so ASAP. According to our release schedule we will be tagging the release candidate for 1.1.1 next Sunday (7/20). We will be asking for wide-spread testing of the release candidate during the week of the 20th.
If you want to open a ticket specifically for this bug-fix release, please use the NumPy 1.1.1 milestone: http://scipy.org/scipy/numpy/milestone/1.1.1
Thanks,
On Sun, Jul 13, 2008 at 01:49:18AM -0700, Jarrod Millman wrote:
The NumPy 1.1.1 release date (7/31/08) is rapidly approaching and we need everyone's help. Chuck Harris has volunteered to take the lead on coordinating this release.
Anybody has an idea what the status is on #844? ( http://scipy.org/scipy/numpy/ticket/844 )
Cheers,
Gaël
On Mon, Jul 14, 2008 at 10:50 PM, Gael Varoquaux < gael.varoquaux@normalesup.org> wrote:
On Sun, Jul 13, 2008 at 01:49:18AM -0700, Jarrod Millman wrote:
The NumPy 1.1.1 release date (7/31/08) is rapidly approaching and we need everyone's help. Chuck Harris has volunteered to take the lead on coordinating this release.
Anybody has an idea what the status is on #844? ( http://scipy.org/scipy/numpy/ticket/844 )
I suspect it is a blas problem, it doesn't show up here. David?
Chuck
On Tue, Jul 15, 2008 at 2:01 PM, Charles R Harris charlesr.harris@gmail.com wrote:
On Mon, Jul 14, 2008 at 10:50 PM, Gael Varoquaux gael.varoquaux@normalesup.org wrote:
On Sun, Jul 13, 2008 at 01:49:18AM -0700, Jarrod Millman wrote:
The NumPy 1.1.1 release date (7/31/08) is rapidly approaching and we need everyone's help. Chuck Harris has volunteered to take the lead on coordinating this release.
Anybody has an idea what the status is on #844? ( http://scipy.org/scipy/numpy/ticket/844 )
I suspect it is a blas problem, it doesn't show up here. David?
I believe it is a bug in ATLAS:
http://math-atlas.sourceforge.net/errata3.8.0.html#RMAAT
Unfortunately, this means I have to rebuild atlas on windows, which will take time ...
cheers,
David
participants (6)
-
Charles R Harris -
David Cournapeau -
Gael Varoquaux -
Jarrod Millman -
Sebastian Haase -
Stéfan van der Walt