You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Python 2 reaching EOL on 1/1/2020, bottleneck will also be dropping support for Python 2.7.
With the recent adoption of NEP 29, numpy has adopted a formal version upgrade cadence. Given bottleneck's tight compatibility with numpy, it likely makes sense for us to adopt NEP 29 as well. The relevant section is the following timeline:
This would imply dropping 3.5 support in the next release as well. We would not be doing anything to actively inhibit use on 3.5, just not actively testing or seeking to fix issues that solely exhibit there.
Please reach out in this thread if this would inhibit your use of bottleneck. If there is no general objection, I will adopt NEP 29 around 1/1/2020.
The text was updated successfully, but these errors were encountered:
With Python 2 reaching EOL on 1/1/2020,
bottleneck
will also be dropping support for Python 2.7.With the recent adoption of NEP 29,
numpy
has adopted a formal version upgrade cadence. Givenbottleneck
's tight compatibility withnumpy
, it likely makes sense for us to adopt NEP 29 as well. The relevant section is the following timeline:This would imply dropping 3.5 support in the next release as well. We would not be doing anything to actively inhibit use on 3.5, just not actively testing or seeking to fix issues that solely exhibit there.
Please reach out in this thread if this would inhibit your use of
bottleneck
. If there is no general objection, I will adopt NEP 29 around 1/1/2020.The text was updated successfully, but these errors were encountered: