Juan made a pretty good argument for keeping 3.6 support in the next
scikit-image release, let me try to paraphrase:
- Since nobody has made the PR to explicitly drop python 3.6 from the
scikit-image build matrix, we will continue to support it, but if somebody
were to make the PR, I (Juan) would
Hi. On behalf of Quansight and RTOSHoldings, I would like to introduce
"pnumpy", a package to speed up NumPy.
https://quansight.github.io/numpy-threading-extensions/stable/index.html
What is in it?
- use "PyUFunc_ReplaceLoopBySignature" to hook all the UFunc inner loops
- When the inner loop
I am in favor of dropping py36 for np1.20, I think it would be good to lead
by example.
Similar to pandas, the next Matplotlib release (3.4 targeted for Dec/Jan)
will not support py36.
Tom
On Tue, Nov 3, 2020 at 9:18 AM Mark Harfouche
wrote:
> Juan made a pretty good argument for keeping 3.6
Hi,
For what it's worth, python 3.6 is also dropped for astropy 4.2 (RC1 to be
released in the next few days). We haven't yet formally adopted NEP29, but
are very close to it peding some word smithing, and no one from the dev
team was fighting for keeping support for 3.6. or numpy 1.16.
Cheers,
Hi all,
Our bi-weekly triage-focused NumPy development meeting is today
(Wednesday, November 4th) at 11 am Pacific Time (18:00 UTC).
Everyone is invited to join in and edit the work-in-progress meeting
topics and notes:
https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg
I encourage everyone to notify us of
