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
setuptools scm workaround doesnt work for packages with dashes in the name #145
Comments
I faced pypa/setuptools_scm#630 only recently. However, @RonnyPfannschmidt made a quick investigation that led me here. I am not sure whether a dash should or should not be part of a source distribution name, but it seems to be a fairly common practice to use dashes in the name. In fact, the same is done in Line 29 in 7c4403a
As pointed out above, the code here assumes that there would not be any dashes in the file name. check-manifest/check_manifest.py Line 882 in 7c4403a
Knowing that setuptools version strings do not contain extra dashes, this could be replaced with the following return filename.split('-')[-1] I have tested a build containing this change with my setup, and the tests provided with this repo. It is working as expected now. Was there a specific reason or motivation to use the |
Should be fixed by #146. |
Fix released in check-manifest 0.47. |
the fix of #68 doesn't notify the user that it uses pretend_version,, and incorrectly puts in a bad version number
this triggers pypa/setuptools_scm#630
as https://github.com/zobayer1/logging-extras has in fact a extra dash
its ABSOLUTELY necessary to inform the users if something like
SETUPTOOLS_SCM_PRETEND_VERSION
is setadditionally its not safe to use for build processes that actually install dependencies (as any pulled sdist that wants setuptools_scm may get misinformed about their versions
check-manifest/check_manifest.py
Lines 877 to 882 in 7c4403a
and then
check-manifest/check_manifest.py
Line 977 in 7c4403a
The text was updated successfully, but these errors were encountered: