> 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 ? -- M On Mon, Nov 13, 2017 at 12:11 AM, Daπid <davidmen...@gmail.com> wrote: > On 10 November 2017 at 23:03, Robert McLeod <robbmcl...@gmail.com> wrote: >> >> E.g. in `requirements.txt`: >> >> numpy; python_version>"3.0" >> numpylts; python_version<"3.0" >> >> In both cases you still call `import numpy` in the code. > > > 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? > > /David. > > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@python.org > https://mail.python.org/mailman/listinfo/numpy-discussion > _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
