Update to setup.cfg potentially required about wrapt HOT 4 CLOSED

How does this affect old release wheels on PyPi?

People using tensorflow are pinned to an older version of wrapt. Will this mean their installs will start failing if I don't go back and create a new patch release of older versions. That is going to be almost impossible as GitHub actions doesn't support some older Python versions anymore and creating a patch release which drops Python versions may not be appreciated.

from wrapt.

I have no idea sorry. You'll probably need to reach out to the setuptools maintainers.

While it will probably be painful to support older versions, it would probably still be useful to some if there was a brand new latest version provided that is compatible with the upcoming changes.

Or perhaps this is good motivation to move away from setuptools and on to something like Poetry or Flit?

from wrapt.

That warning also says "remove deprecated calls", which could be bad wording, but I don't think that part of the warning applies to the keyword arguments. I feel it may relate more to the actual removal of distutils in Python 3.12. So expectation is that don't use any functions or objects from distutils as mentioned in:

• https://setuptools.pypa.io/en/latest/deprecated/distutils-legacy.html#prefer-setuptools

For the keywords, although docs mention as deprecated, I don't actually think they will remove the old ones and can't find anything that says they will. It has too big a risk of breaking old packages even when they use setuptools.

Anyway, suggest you try installing:

• https://pypi.org/project/wrapt/1.16.0rc1/

This has dropped distutils and requires setuptools. You may find that the warning above is different or disappears at normal log levels. If you do try, let me know what message you get with it so know if different.

BTW, this doesn't mean I will not change the keyword argument, just trying to understand what is really meant by the warning at this point and implications on older released packages. For now I don't think older released packages will be affected as they are Python 3.11 or older and any change is only going to relate to some possible version of Python 3.12.

from wrapt.

Have changed to use license_files in 1.16.0.

from wrapt.