You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I pointed out in this message, it seems that this project is unclear on what its name is. Historically, the name has been setuptools_scm, but with the 8.0 release and the move to pyproject.toml, the project renamed to setuptools-scm, but kept the name setuptools_scm in other places.
Incidentally, the project also seems to have had setuptools-scm as the indicated name (pre-normalized) in the wheels for versions prior to 8.0 as well. It'd be interesting to know why that is.
I'm not particularly interested in what the name of the project is, but I am interested in being consistent about it and avoiding being capriciously inconsistent just because the normalization allows it.
The text was updated successfully, but these errors were encountered:
lets migrate names to the normalized name for consistency for all paces where its not a import name or entry-point name
I'll leave [tool.setuptools_scm] alone for now, too. We can maybe take advantage of the name mismatch to utilize [tool.setuptools-scm] for a different purpose (as a section heading without implying behavior).
jaraco
added a commit
to jaraco/setuptools-scm
that referenced
this issue
Aug 13, 2024
As I pointed out in this message, it seems that this project is unclear on what its name is. Historically, the name has been
setuptools_scm
, but with the 8.0 release and the move to pyproject.toml, the project renamed tosetuptools-scm
, but kept the namesetuptools_scm
in other places.Incidentally, the project also seems to have had
setuptools-scm
as the indicated name (pre-normalized) in the wheels for versions prior to 8.0 as well. It'd be interesting to know why that is.I'm not particularly interested in what the name of the project is, but I am interested in being consistent about it and avoiding being capriciously inconsistent just because the normalization allows it.
The text was updated successfully, but these errors were encountered: