-
-
Notifications
You must be signed in to change notification settings - Fork 221
pyproject.toml does not contain a tool.setuptools_scm section #953
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
Comments
Related issue: #938 |
Would a log level of info be sufficient? |
I just tested and yes, |
this ensures we dont spam projects
What is the reason why this log entry is written (warning level or not)? Does it check if |
Sorry, but 517ed80 is still wrong: when my project doesn’t use |
Setuptools has no safe way to control the file finder entry point |
I am sorry, but could you elaborate a bit, I really don’t understand what do you mean and how it is relevant to my complaint? |
Setuptools always considers all plugins, there's no way to opt out easily You shouldn't be seeing the indo log in most cases If you do please elaborate on environment and context in a new issue |
I'm packaging various Python projects for OpenIndiana. The packaging (and especially testing) is done in real environment with possibly many unrelated packages installed to make sure the packaged project works properly once it is installed.
When I try to work with a project that does not use
setuptools_scm
andsetuptools_scm
is installed then I see this warning:The warning is seen in many logs, including testing log. This causes a problem to us because it raises errors when we compare test logs between test runs. Yes, we could add a special rule to our testing logic to filter out this warning, but since this is a regression from
setuptools_scm==7.1.0
then I'd prefer to see it fixed/changed at thesetuptools_scm
side.Possible solution would be to change
log.warning(e)
tolog.debug(e)
in the setuptools.py file. If that's not possible or desirable then what about to implement some way how to silence the warning using an environment variable?Thank you.
The text was updated successfully, but these errors were encountered: