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
pyproject.toml configuration error for dash-separated module name #4316
Comments
Yes that is possible. Currently the definition comes from: and I will probably select or define a new format for this (should it be any kind of string or merely accept Is this something we also want to apply to |
I thought about this a bit and i do think it makes sense to apply the same to packages, for symmetry and also because Python supports it:
I have confirmed that Python also supports If you want to be extremely permissive, it sounds as if only disallowing My instinct, though, is to limit to just |
The pip-run project defines a py-module that has a dash in the name. It does so intentionally in order to make it possible to type
python -m pip-run
without having to enter any chorded characters (-
is roughly 1/3 as expensive as_
).After converting the config to pyproject.toml, however, this value is rejected by policy.
I can understand why "python-module-name" seemed like a good reasonableness check, but it turns out to be backward incompatible and unnecessarily constraining against a use-case like above.
Can we back out this change and make it lenient as it was with setup.cfg?
The text was updated successfully, but these errors were encountered: