On Fri, May 27, 2022 at 6:00 AM Aaron Meurer wrote:
>
>
> 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
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
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 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
I created https://github.com/numpy/numpy/pull/21601 to update NEP29 to
address PEP602.
I'm not sure what the procedure for updating the NEP is. What I wrote may
be too editorial, we could amend it to "PEP602 changed cadence, we are not
reacting." with no explanation as well.
Tom
On Wed, May
> 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 makes sense to shorten the time window. I also don't
On Wed, 25 May 2022, 4:54 pm Thomas Caswell, wrote:
>
> Stealing some language/concepts from Microsoft (if I recall it correctly),
> we should sort out which entries in that support matrix are Level 1 (CI +
> wheels), Level 2 (CI), Level 3 (we test something that looks like this),
> and Level 4
On Wed, May 25, 2022 at 4:56 PM Thomas Caswell wrote:
> To reiterate what Ralf said, the possibility of Python going to a faster
> cadence was one of the things on our mind when drafting NEP 29 (see
> https://numpy.org/neps/nep-0029-deprecation_policy.html#n-minor-versions-of-python
> for why
To reiterate what Ralf said, the possibility of Python going to a faster
cadence was one of the things on our mind when drafting NEP 29 (see
https://numpy.org/neps/nep-0029-deprecation_policy.html#n-minor-versions-of-python
for why did not go with a fixed number of versions) because the reality of
On Tue, May 24, 2022 at 3:24 PM Ewout ter Hoeven <
e.m.terhoe...@student.tudelft.nl> wrote:
> Personally I would be in favor of updating NEP 29 to a support timespan in
> which at most 3 (minor) Python versions are supported. The development of
> Python is still at a high pace and NumPy is a high
Personally I would be in favor of updating NEP 29 to a support timespan in
which at most 3 (minor) Python versions are supported. The development of
Python is still at a high pace and NumPy is a high performance library which
thrives when be able to adopt the latest Python features and having
On Thu, Apr 7, 2022 at 5:42 PM Charles R Harris
wrote:
>
>
> On Wed, Apr 6, 2022 at 3:06 PM Aaron Meurer wrote:
>
>> Was the faster CPython release cadence (PEP 602
>> https://peps.python.org/pep-0602/) ever discussed in relation to NEP
>> 29
On Wed, Apr 6, 2022 at 3:06 PM Aaron Meurer wrote:
> Was the faster CPython release cadence (PEP 602
> https://peps.python.org/pep-0602/) ever discussed in relation to NEP
> 29 (https://numpy.org/neps/nep-0029-deprecation_policy.html)?
>
> NEP 29 currently says:
>
> "The current Python release
14 matches
Mail list logo
