On Nov 12, 2017 1:12 PM, "Todd" <toddrjen@gmail.com> wrote:

Might it make sense to do this in a synchronized manner with scipy? So both numpy and scipy drop support for python 2 on the first release after December 31 2018, and numpy's first python3-only release comes before (or simultaneously with) scipy's. Then scipy can set is minimum supported numpy version to be the first python3-only version.

That allows scipy to have a clean, obvious point where scipy supports only the latest numpy. This will diverge later, but it seems to be a relatively safe place to bring them back into sync.

That's really a question for the scipy devs on the scipy mailing list. There's substantial overlap between the numpy and scipy communities, but not everyone is on both lists and they're distinct projects that sometimes have unique issues to worry about.

I'd like to see numpy's downstream projects become more aggressive about dropping support for old numpy versions in general, but there's no technical reason that scipy's first 3-only release couldn't continue to support one or more numpy 2+3 releases.

-n