-
-
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
SpecifierSet has no attribute split #1869
Comments
But wait - if 'check_specifier' is called when a declarative 'python_requires' is indicated, then how is it that invalid specifiers were allowed in the bug (#1787)? |
Oh, nevermind. It looks like cheroot is doing something weird in its setup.py. |
Please reopen this, we need a workaround as it break lots and lots of projects. |
@ssbarnea it only breaks hacks |
Indeed, I'm extremely reluctant to support projects that wish to read declarative config on their own. I suggest if you wish to continue to read declarative config and pass it into |
Manually parsing setup.cfg and passing the parsed data into the setup function is not officially supported by setuptools (see pypa/setuptools#1869) and is also unnecessary, because the setup function will automatically read the relevant data from setup.cfg.
Reading setup.cfg manually is not supported by setuptools and causes errors with some setup.cfg features (see pypa/setuptools#1869). The supported way to use setup.cfg is to call setup() with no arguments and let setuptools read and parse setup.cfg itself.
Running the tests on cheroot, I'm seeing this error:
I suspect this issue is brought about by #1847, and what's happening is the declarative config python_requires is transforming the value and later the value is parsed again. This code illustrates how the same error is elicited by a double construction:
The text was updated successfully, but these errors were encountered: