On Thu, May 26, 2022 at 3:45 AM Matti Picus wrote:
> On 26/5/22 05:40, Aaron Meurer wrote:
>
> >> We cannot do that (yet, at least). Failing to publish wheels for a
> supported Python version on a major OS is far worse than dropping support
> completely. This will remain true until the time that
Hi All,
On behalf of the NumPy team, I'm pleased to announce the release of NumPy
1.23.0rc1. The NumPy 1.23.0 release continues the ongoing work to improve
the handling and promotion of dtypes, increase the execution speed, clarify
the documentation, and expire old deprecations. The highlights
https://github.com/numpy/numpy/pull/21601 has been merged, but we should
make sure everyone is on board with the updated wording. The intent was to
resolve the discrepancy I think Aaron is referring to (the text spoke of
the 18mo release cycle in present tense) and to justify sticking with
On Thu, May 26, 2022 at 3:19 PM wrote:
> Thank you Gommers
>
> I'd like to discuss this again when I finish SVE implementation. (It may
> be one month later.)
>
Sounds great, thanks Kentaro.
Cheers,
Ralf
> Cheers,
> Kentaro
> ___
> NumPy-Discussion
Thank you Gommers
I'd like to discuss this again when I finish SVE implementation. (It may be one
month later.)
Cheers,
Kentaro
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to
On Thu, May 26, 2022 at 4:41 AM Aaron Meurer wrote:
> > I have seen problems popping up already in a few places with latest
> numpy not supported what is still the most commonly used Python version
> (don't have links, sorry - but they were real packaging-related issues). So
> I don't think it
On 26/5/22 05:40, Aaron Meurer wrote:
We cannot do that (yet, at least). Failing to publish wheels for a supported
Python version on a major OS is far worse than dropping support completely.
This will remain true until the time that Pip starts defaulting to wheels-only
and never picks the
