Making a 1.13.2 release

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Making a 1.13.2 release

Charles R Harris
Hi All,

I've delayed the NumPy 1.13.2 release hoping for Python 3.6.2 to show up fixing #29943  so we can close #9272, but the Python release has been delayed to July 11 (expected). The Python problem means that NumPy compiled with Python 3.6.1 will not run in Python 3.6.0. However, I've also been asked to have a bugfixed version of 1.13 available for Scipy 2017 next week. At this point it looks like the best thing to do is release 1.13.1 compiled with Python 3.6.1 and ask folks to upgrade Python if they have a problem, and then release 1.13.2 as soon as 3.6.2 is released.

Thoughts?

Chuck

_______________________________________________
NumPy-Discussion mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/numpy-discussion
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Making a 1.13.2 release

Matthew Brett
Hi,

On Thu, Jul 6, 2017 at 2:10 PM, Charles R Harris
<[hidden email]> wrote:

> Hi All,
>
> I've delayed the NumPy 1.13.2 release hoping for Python 3.6.2 to show up
> fixing #29943  so we can close #9272, but the Python release has been
> delayed to July 11 (expected). The Python problem means that NumPy compiled
> with Python 3.6.1 will not run in Python 3.6.0. However, I've also been
> asked to have a bugfixed version of 1.13 available for Scipy 2017 next week.
> At this point it looks like the best thing to do is release 1.13.1 compiled
> with Python 3.6.1 and ask folks to upgrade Python if they have a problem,
> and then release 1.13.2 as soon as 3.6.2 is released.

I think this problem only applies to Windows.  We might be able to
downgrade the Appveyor Python 3.6.1 to 3.6.0 for that - I can look
into it today if it would help.

While I'm at it - how about switching to OpenBLAS wheels on Windows
for this release?

Cheers,

Matthew
_______________________________________________
NumPy-Discussion mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/numpy-discussion
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Making a 1.13.2 release

Charles R Harris


On Thu, Jul 6, 2017 at 7:15 AM, Matthew Brett <[hidden email]> wrote:
Hi,

On Thu, Jul 6, 2017 at 2:10 PM, Charles R Harris
<[hidden email]> wrote:
> Hi All,
>
> I've delayed the NumPy 1.13.2 release hoping for Python 3.6.2 to show up
> fixing #29943  so we can close #9272, but the Python release has been
> delayed to July 11 (expected). The Python problem means that NumPy compiled
> with Python 3.6.1 will not run in Python 3.6.0. However, I've also been
> asked to have a bugfixed version of 1.13 available for Scipy 2017 next week.
> At this point it looks like the best thing to do is release 1.13.1 compiled
> with Python 3.6.1 and ask folks to upgrade Python if they have a problem,
> and then release 1.13.2 as soon as 3.6.2 is released.

I think this problem only applies to Windows.  We might be able to
downgrade the Appveyor Python 3.6.1 to 3.6.0 for that - I can look
into it today if it would help.

While I'm at it - how about switching to OpenBLAS wheels on Windows
for this release?

Cheers,

Matthew

Haste makes waste ;) I'd rather put off the move to OpenBlas to 1.14 to allow more time for it to settle, and compiling against Python 3.6.0 seems like more work than it is worth, It should be easy to upgrade to 3.6.1 for those affected once they are aware of the problem, and it should not be too long before Python 3.6.2 is out. I'll call it the Scipy2017 release.

Chuck



_______________________________________________
NumPy-Discussion mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/numpy-discussion
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Making a 1.13.2 release

Matthew Brett
On Thu, Jul 6, 2017 at 3:37 PM, Charles R Harris
<[hidden email]> wrote:

>
>
> On Thu, Jul 6, 2017 at 7:15 AM, Matthew Brett <[hidden email]>
> wrote:
>>
>> Hi,
>>
>> On Thu, Jul 6, 2017 at 2:10 PM, Charles R Harris
>> <[hidden email]> wrote:
>> > Hi All,
>> >
>> > I've delayed the NumPy 1.13.2 release hoping for Python 3.6.2 to show up
>> > fixing #29943  so we can close #9272, but the Python release has been
>> > delayed to July 11 (expected). The Python problem means that NumPy
>> > compiled
>> > with Python 3.6.1 will not run in Python 3.6.0. However, I've also been
>> > asked to have a bugfixed version of 1.13 available for Scipy 2017 next
>> > week.
>> > At this point it looks like the best thing to do is release 1.13.1
>> > compiled
>> > with Python 3.6.1 and ask folks to upgrade Python if they have a
>> > problem,
>> > and then release 1.13.2 as soon as 3.6.2 is released.
>>
>> I think this problem only applies to Windows.  We might be able to
>> downgrade the Appveyor Python 3.6.1 to 3.6.0 for that - I can look
>> into it today if it would help.
>>
>> While I'm at it - how about switching to OpenBLAS wheels on Windows
>> for this release?
>>
>> Cheers,
>>
>> Matthew
>
>
> Haste makes waste ;) I'd rather put off the move to OpenBlas to 1.14 to
> allow more time for it to settle,

I'd only say that I don't know of any settling that is likely to
happen.  I suspect that not many people have tried the experimental
wheels.   I've automated the build process both for OpenBLAS and the
OpenBLAS wheels, and I believe those are solid now.

> and compiling against Python 3.6.0 seems
> like more work than it is worth,

Probably about two hours of futzing on Appveyor - your call - I'm
happy not to do it :)

Cheers,

Matthew
_______________________________________________
NumPy-Discussion mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/numpy-discussion
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Making a 1.13.2 release

Charles R Harris


On Thu, Jul 6, 2017 at 9:53 AM, Matthew Brett <[hidden email]> wrote:
On Thu, Jul 6, 2017 at 3:37 PM, Charles R Harris
<[hidden email]> wrote:
>
>
> On Thu, Jul 6, 2017 at 7:15 AM, Matthew Brett <[hidden email]>
> wrote:
>>
>> Hi,
>>
>> On Thu, Jul 6, 2017 at 2:10 PM, Charles R Harris
>> <[hidden email]> wrote:
>> > Hi All,
>> >
>> > I've delayed the NumPy 1.13.2 release hoping for Python 3.6.2 to show up
>> > fixing #29943  so we can close #9272, but the Python release has been
>> > delayed to July 11 (expected). The Python problem means that NumPy
>> > compiled
>> > with Python 3.6.1 will not run in Python 3.6.0. However, I've also been
>> > asked to have a bugfixed version of 1.13 available for Scipy 2017 next
>> > week.
>> > At this point it looks like the best thing to do is release 1.13.1
>> > compiled
>> > with Python 3.6.1 and ask folks to upgrade Python if they have a
>> > problem,
>> > and then release 1.13.2 as soon as 3.6.2 is released.
>>
>> I think this problem only applies to Windows.  We might be able to
>> downgrade the Appveyor Python 3.6.1 to 3.6.0 for that - I can look
>> into it today if it would help.
>>
>> While I'm at it - how about switching to OpenBLAS wheels on Windows
>> for this release?
>>
>> Cheers,
>>
>> Matthew
>
>
> Haste makes waste ;) I'd rather put off the move to OpenBlas to 1.14 to
> allow more time for it to settle,

I'd only say that I don't know of any settling that is likely to
happen.  I suspect that not many people have tried the experimental
wheels.   I've automated the build process both for OpenBLAS and the
OpenBLAS wheels, and I believe those are solid now.

But it does add risk. We can deal with that in a regular release because of the betas and release condidates, but I'm not counting on any of those for 1.13.1 (2).

Chuck
 

_______________________________________________
NumPy-Discussion mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/numpy-discussion
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Making a 1.13.2 release

Chris Barker - NOAA Federal
In reply to this post by Charles R Harris
On Thu, Jul 6, 2017 at 6:10 AM, Charles R Harris <[hidden email]> wrote:
I've delayed the NumPy 1.13.2 release hoping for Python 3.6.2 to show up fixing #29943  so we can close #9272, but the Python release has been delayed to July 11 (expected). The Python problem means that NumPy compiled with Python 3.6.1 will not run in Python 3.6.0.

If it's compiled against 3.6.0 will it work fine with 3.6.1? and probably 3.6.2 as well?

If so, it would be nice to do it that way, if Matthew doesn't mind :-)

But either way, it'll be good to get it out.

Thanks!

-CHB

 
However, I've also been asked to have a bugfixed version of 1.13 available for Scipy 2017 next week. At this point it looks like the best thing to do is release 1.13.1 compiled with Python 3.6.1 and ask folks to upgrade Python if they have a problem, and then release 1.13.2 as soon as 3.6.2 is released.

Thoughts?

Chuck

_______________________________________________
NumPy-Discussion mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/numpy-discussion




--

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

[hidden email]

_______________________________________________
NumPy-Discussion mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/numpy-discussion
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Making a 1.13.2 release

Nathaniel Smith
In reply to this post by Charles R Harris
It's also possible to work around the 3.6.1 problem with a small preprocessor hack. On my phone but there's a link in the bug report discussion.

On Jul 6, 2017 6:10 AM, "Charles R Harris" <[hidden email]> wrote:
Hi All,

I've delayed the NumPy 1.13.2 release hoping for Python 3.6.2 to show up fixing #29943  so we can close #9272, but the Python release has been delayed to July 11 (expected). The Python problem means that NumPy compiled with Python 3.6.1 will not run in Python 3.6.0. However, I've also been asked to have a bugfixed version of 1.13 available for Scipy 2017 next week. At this point it looks like the best thing to do is release 1.13.1 compiled with Python 3.6.1 and ask folks to upgrade Python if they have a problem, and then release 1.13.2 as soon as 3.6.2 is released.

Thoughts?

Chuck

_______________________________________________
NumPy-Discussion mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/numpy-discussion


_______________________________________________
NumPy-Discussion mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/numpy-discussion
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Making a 1.13.2 release

Juan Nunez-Iglesias
Just chiming in with a +1 to releasing 1.13.1 before SciPy. It will certainly save the skimage tutorial a lot of headaches! Not that I’ll be there but I look out for my own. =P

On 7 Jul 2017, 3:54 AM +1000, Nathaniel Smith <[hidden email]>, wrote:
It's also possible to work around the 3.6.1 problem with a small preprocessor hack. On my phone but there's a link in the bug report discussion.

On Jul 6, 2017 6:10 AM, "Charles R Harris" <[hidden email]> wrote:
Hi All,

I've delayed the NumPy 1.13.2 release hoping for Python 3.6.2 to show up fixing #29943  so we can close #9272, but the Python release has been delayed to July 11 (expected). The Python problem means that NumPy compiled with Python 3.6.1 will not run in Python 3.6.0. However, I've also been asked to have a bugfixed version of 1.13 available for Scipy 2017 next week. At this point it looks like the best thing to do is release 1.13.1 compiled with Python 3.6.1 and ask folks to upgrade Python if they have a problem, and then release 1.13.2 as soon as 3.6.2 is released.

Thoughts?

Chuck

_______________________________________________
NumPy-Discussion mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/numpy-discussion
Loading...