Originally reported by: jaraco (Bitbucket: jaraco, GitHub: jaraco)
With the release of 3.0, it became apparent that the DeprecationWarning for #65 wasn't adequate to raise awareness of the pending removal.
Setuptools should probably enforce visibility of DeprecationWarnings in the setuptools and pkg_resources namespaces.
Something like
warnings.filterwarnings("always", category=DeprecationWarning, module="setuptools\.|pkg_resources\.")
I'm not quite sure yet where this would happen. I'm considering it could happen at import time or possibly only during select commands initialization.
Originally reported by: jaraco (Bitbucket: jaraco, GitHub: jaraco)
With the release of 3.0, it became apparent that the DeprecationWarning for #65 wasn't adequate to raise awareness of the pending removal.
Setuptools should probably enforce visibility of DeprecationWarnings in the setuptools and pkg_resources namespaces.
Something like
I'm not quite sure yet where this would happen. I'm considering it could happen at import time or possibly only during select commands initialization.