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.
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_scmandsetuptools_scmis 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.0then I'd prefer to see it fixed/changed at thesetuptools_scmside.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.