-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid UserWarnings emitted when calling into distutils.dist.Distribution #29
Comments
Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco): Indeed, setuptools just passes the attributes through directly through to Distribution. It will be somewhat challenging for setuptools to track which attributes might be valid for a distutils Distribution. Or perhaps setuptools can simply suppress that warning around the call to the superclass. |
Original comment by sorin (Bitbucket: sorin, GitHub: sorin): Is there a way to disable these warnings from inside the setup.py file? I get very annoying false warnings like:
|
Original comment by stefanholek (Bitbucket: stefanholek, GitHub: stefanholek): Perhaps you are looking for https://docs.python.org/3/library/warnings.html#warning-filter |
Original comment by sorin (Bitbucket: sorin, GitHub: sorin): Isn't this a problem with setuptools itself, that it should just ignore unknown distribution options? Otherwise it would be impossible to hide these messages and it will alienate all users. Is exactly the opposite of an deprecated warning: you are notifying the users about something that is newer than his tools. Obviously there is nothing they can do about it. |
ENH: use #!/usr/bin/env python for the shebang instead of non-working on POSIX systems plain #!python
Originally reported by: ncoghlan (Bitbucket: ncoghlan, GitHub: ncoghlan)
Currently setuptools.dist.Distribution passes the unfiltered collection of keyword arguments up to distutils.core.Distribution. This results in lots of scary looking "UserWarning" messages when you actually use the setuptools-only options (see http://stackoverflow.com/questions/8295644/pypi-userwarning-unknown-distribution-option-install-requires)
It also makes it look like you're calling distutils rather than setuptools, since the stack trace (showing that this is a call up into setuptools) isn't visible.
For example, cleaning coverage.py for devinabox looks like this:
But if we make those errors, we see that it is picking up the symlinked setuptools correctly:
The text was updated successfully, but these errors were encountered: