-
-
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
Option 'python_requires' is not supported in configuration files #999
Comments
It's probably a design flaw that these option definitions need to be defined in two places, but that's what we've got. Would you consider creating a PR to address the missing option?
That does seem like a defect, but perhaps ignorable. I can see how one might want to define the 'author' or 'maintainer' as users settings, though that does have some nasty implications around replicable builds. I don't think it was intentional that these other files are honored for these settings. |
PR #1007 created. |
Fixes #999: support python_requires and py_modules in configuration files
The option
python_requires
is not supported when metadata / options are loaded fromsetup.cfg
via #862.On a side note: Is it intended behavior that those package specific metadata / options may be given in all configuration files given by
distutils.core.Distribution.find_config_files
(i.e. including the user's.pydistutils.cfg
, which is not specific to the package)?The text was updated successfully, but these errors were encountered: