On Sun, Aug 21, 2022 at 6:36 PM Ralf Gommers <[email protected]> wrote:
> Hi all, > > After setuptools 65.0 was released a few days ago, all users of > numpy.distutils had their builds broken. This is already fixed in > setuptools 65.0.2 because the breakage was particularly bad. However, the > next breakage may not be fixed anymore (and more breakages *are* expected). > So this is a good time to remind you all that you should put an upper bound > on the setuptools version you allow in the releases of your package - to > the last version that is known to work with your package. > > Our official stance here is that setuptools versions >=60 are not > supported - see the "deprecating numpy.distutils" thread: > https://mail.python.org/archives/list/[email protected]/message/PMU4P4YRP2FZA2Z6Z6Z74ZFYD6PCRXQ5/. > Newer versions may work for you, depending on what features you use. They > don't for NumPy and for SciPy; both projects pin to 59.X to avoid problems. > > For the recent issue with setuptools 65.0.0, see > https://github.com/numpy/numpy/issues/22135. We have also made the > warnings about this topic in our docs more explicit, see > https://github.com/numpy/numpy/pull/22154. > > Cheers, > Ralf > > > _______________________________________________ > NumPy-Discussion mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > Member address: [email protected] Is there a good way to pin <2 this when using oldest-supported-numpy? -Kevin
_______________________________________________ NumPy-Discussion mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: [email protected]
