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

[Matthias Bussonnier]

>  The trouble is PyPi doesn't allow multiple branches.  So if you upload NumPy 2.0 wheels, then you cannot turn around and upload 1.18.X bug-fix patches.  At least, this is my understanding of PyPi.

That's perfectly feasible. We've been maintaining a 6.x (Python 3
only) and 5.x (Python2+3) of IPython for about a year now.
-- 
M

On Mon, Nov 13, 2017 at 10:08 AM, Robert McLeod <robbmcleod at gmail.com> wrote:
>
>
> On Mon, Nov 13, 2017 at 7:47 AM, Matthias Bussonnier
> <bussonniermatthias at gmail.com> wrote:
>>
>> > For this to be efficient, it should be done soon enough to allow
>> > downstream projects to adapt their requirements.txt.
>> > Release managers: how much more effort would it be to upload current
>> > numpy to both numpy and numpylts?
>>
>> I'm not quite sure I see the point. you would ask downstream to change
>> `numpy` to `numpylts` instead of  `numpy` to `numpy<2` ?
>>
>> Also I think then you have the risk of having for example pandas
>> saying `numpy<2` and scipy saying `numpylts` and now the pasckages are
>> incompatible ?
>
>
>  The trouble is PyPi doesn't allow multiple branches.  So if you upload
> NumPy 2.0 wheels, then you cannot turn around and upload 1.18.X bug-fix
> patches.  At least, this is my understanding of PyPi.
>
>
>
> --
> Robert McLeod, Ph.D.
> robbmcleod at gmail.com
> robbmcleod at protonmail.com
> www.entropyreduction.al
>
>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>