Re: [Numpy-discussion] Proposal of timeline for dropping Python 2.7 support

2017-11-14 Thread Nathaniel Smith
Apparently this is actually uncontroversial, the discussion's died
down (see also the comments on Chuck's PR [1]), and anyone who wanted
to object has had more than a week to do so, so... I guess we can say
this is what's happening and start publicizing it to our users!

A direct link to the rendered NEP in the repo is:
https://github.com/numpy/numpy/blob/master/doc/neps/dropping-python2.7-proposal.rst

(I guess that at some point it will also show up on docs.scipy.org.)

-n

[1] https://github.com/numpy/numpy/pull/10006

On Thu, Nov 9, 2017 at 5:52 PM, Nathaniel Smith  wrote:
> Fortunately we can wait until we're a bit closer before we have to
> make any final decision on the version numbering :-)
>
> Right now though it would be good to start communicating to
> users/downstreams about whatever our plans our though, so they can
> make plans. Here's a first attempt at some text we can put in the
> documentation and point people to -- any thoughts, on either the plan
> or the wording?
>
>  DRAFT TEXT - NOT FINAL - DO NOT POST THIS TO HACKERNEWS OK? OK 
>
> The Python core team plans to stop supporting Python 2 in 2020. The
> NumPy project has supported both Python 2 and Python 3 in parallel
> since 2010, and has found that supporting Python 2 is an increasing
> burden on our limited resources; thus, we plan to eventually drop
> Python 2 support as well. Now that we're entering the final years of
> community-supported Python 2, the NumPy project wants to clarify our
> plans, with the goal of to helping our downstream ecosystem make plans
> and accomplish the transition with as little disruption as possible.
>
> Our current plan is as follows:
>
> Until **December 31, 2018**, all NumPy releases will fully support
> both Python 2 and Python 3.
>
> Starting on **January 1, 2019**, any new feature releases will support
> only Python 3.
>
> The last Python-2-supporting release will be designated as a long-term
> support (LTS) release, meaning that we will continue to merge
> bug-fixes and make bug-fix releases for a longer period than usual.
> Specifically, it will be supported by the community until **December
> 31, 2019**.
>
> On **January 1, 2020** we will raise a toast to Python 2, and
> community support for the last Python-2-supporting release will come
> to an end. However, it will continue to be available on PyPI
> indefinitely, and if any commercial vendors wish to extend the LTS
> support past this point then we are open to letting them use the LTS
> branch in the official NumPy repository to coordinate that.
>
> If you are a NumPy user who requires ongoing Python 2 support in 2020
> or later, then please contact your vendor. If you are a vendor who
> wishes to continue to support NumPy on Python 2 in 2020+, please get
> in touch; ideally we'd like you to get involved in maintaining the LTS
> before it actually hits end-of-life, so we can make a clean handoff.
>
> To minimize disruption, running 'pip install numpy' on Python 2 will
> continue to give the last working release in perpetuity; but after
> January 1, 2019 it may not contain the latest features, and after
> January 1, 2020 it may not contain the latest bug fixes.
>
> For more information on the scientific Python ecosystem's transition
> to Python-3-only, see: http://www.python3statement.org/
>
> For more information on porting your code to run on Python 3, see:
> https://docs.python.org/3/howto/pyporting.html
>
> 
>
> Thoughts?
>
> -n
>
> On Thu, Nov 9, 2017 at 12:53 PM, Marten van Kerkwijk
>  wrote:
>> In astropy we had a similar discussion about version numbers, and
>> decided to make 2.0 the LTS that still supports python 2.7 and 3.0 the
>> first that does not.  If we're discussing jumping a major number, we
>> could do the same for numpy.  (Admittedly, it made a bit more sense
>> with the numbering scheme astropy had adopted anyway.) -- Marten
>> ___
>> NumPy-Discussion mailing list
>> NumPy-Discussion@python.org
>> https://mail.python.org/mailman/listinfo/numpy-discussion
>
>
>
> --
> Nathaniel J. Smith -- https://vorpus.org



-- 
Nathaniel J. Smith -- https://vorpus.org
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion


[Numpy-discussion] Upcoming revision of the BLAS standard

2017-11-14 Thread Nathaniel Smith
Hi NumPy and SciPy developers,

Apparently there is some work afoot to update the BLAS standard, with
a working document here:

https://docs.google.com/document/d/1DY4ImZT1coqri2382GusXgBTTTVdBDvtD5I14QHp9OE/edit

This seems like something where we might want to get involved in, so
that the new standard works for us, and James Demmel (the first author
on that proposal and a professor here at Berkeley) suggested they'd be
interested to hear our thoughts.

I'm not sure exactly what the process is here -- apparently there have
been some workshops, and there was going to be a BoF today at
Supercomputing, but I don't know what the schedule is or how they'll
be making decisions. It's possible for anyone interested to click on
that google doc above and make "suggestions", but it seems like maybe
it would be useful for the NumPy/SciPy teams to come up with some sort
of shared document on what we want?

I'm really, really not the biggest linear algebra expert on these
lists, so I'm hoping those with more experience will jump in, but to
get started here are some initial ideas for things we might want to
ask for:

- Support for arbitrary strided memory layout
- Replacing xerbla with proper error codes (already in that proposal)
- There's some discussion about NaN handling where I think we might
have opinions. (Am I remember right that currently we have to check
for NaNs ourselves all the time because there are libraries that blow
up if we don't, and we don't know which ones those are?)
- Where the spec ends up giving implementors flexibility, some way to
detect at compile time what options they chose.

-n

-- 
Nathaniel J. Smith -- https://vorpus.org
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion