On Tue, Sep 3, 2024 at 7:53 PM Peter Cock via NumPy-Discussion <
numpy-discussion@python.org> wrote:
> If I recall correctly, people were building against the Numpy 2.0.0
> release candidates in particular. In hindsight keeping those on PyPI might
> have been better. A formal NEP/SPEC seems a good
If I recall correctly, people were building against the Numpy 2.0.0 release
candidates in particular. In hindsight keeping those on PyPI might have
been better. A formal NEP/SPEC seems a good idea.
Peter
On Tue, Sep 3, 2024 at 6:20 PM matti picus wrote:
> I would prefer we never delete packages
I would prefer we never delete packages once we upload them to PyPI,
unless there are security issues with them. As Sean demonstrated,
someone somewhere is going to be using them, and deleting packages
will inevitably break something.
Matti
On Tue, Sep 3, 2024 at 7:44 PM Sean Gillies wrote:
>
>
On Tue, Sep 3, 2024 at 10:46 AM Sean Gillies wrote:
> Hi Chuck,
>
> I've got a version of a package on PyPI that requires Numpy 2.0.0rc1 at
> build time. Not the best decision in hindsight, but I assumed that Numpy
> was the kind of project that wouldn't remove published distributions unless
> th
Hi Chuck,
I've got a version of a package on PyPI that requires Numpy 2.0.0rc1 at
build time. Not the best decision in hindsight, but I assumed that Numpy
was the kind of project that wouldn't remove published distributions unless
there were security issues. It had not up today, right? Would it be
Hi Chuck,
On Tue, Sep 3, 2024, at 08:18, Charles R Harris wrote:
> I just got through deleting a bunch of pre-releases on PyPi and it occurred
> to me that we should have a policy as to what releases should be kept. I
> think that reproducibility requires that we keep all the major and micro
>
