Skip to content

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

Closed
mtelka opened this issue Oct 8, 2023 · 8 comments · Fixed by #996
Closed

pyproject.toml does not contain a tool.setuptools_scm section #953

mtelka opened this issue Oct 8, 2023 · 8 comments · Fixed by #996

Comments

@mtelka
Copy link

mtelka commented Oct 8, 2023

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 and setuptools_scm is installed then I see this warning:

[10/08/23 10:00:26] WARNING  pyproject.toml does not contain a tool.setuptools_scm section                                  setuptools.py:119

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 the setuptools_scm side.

Possible solution would be to change log.warning(e) to log.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.

@mtelka
Copy link
Author

mtelka commented Oct 8, 2023

Related issue: #938

@RonnyPfannschmidt
Copy link
Contributor

Would a log level of info be sufficient?
If its debug it might get lost in the noise

@mtelka
Copy link
Author

mtelka commented Oct 8, 2023

I just tested and yes, log.info is enough.

@fabcor-maxiv
Copy link

What is the reason why this log entry is written (warning level or not)? Does it check if setuptools-scm is listed in build-system.requires?

@mcepl
Copy link

mcepl commented Oct 22, 2024

Sorry, but 517ed80 is still wrong: when my project doesn’t use setuptools_scm at all, why it is even activated, and why is my logging (in whatever level) spammed at all? This is just wrong from the beginning.

@RonnyPfannschmidt
Copy link
Contributor

Setuptools has no safe way to control the file finder entry point

@mcepl
Copy link

mcepl commented Oct 22, 2024

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?

@RonnyPfannschmidt
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants