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
In this case, I would expect that the created version would either something like 1.0.0-devN... or more ideally 1.0.0-foo.devN.
Looking at the code listed in the traceback, it looks like the tool would also choke on any build IDs that were included, though I expect creating a tag with that information would be weird.
I do think that tags with pre-release IDs on them are common enough that I would expect these to work.
The text was updated successfully, but these errors were encountered:
In that case we should throw a better error, the simplified semver only handles numbers
Python versions don't directly support semver data, one is supposed to add that kinda data in local tags (where setuptools _scm could have some better tooling)
Steps to reproduce:
setuptools-scm-4.1.2
1.0.0-foo
I had expected in this case that the tag name would be used as the version (
1.0.0-foo
).A similar exception gets raised looking back toward that tag in a later added commit.
In this case, I would expect that the created version would either something like
1.0.0-devN...
or more ideally1.0.0-foo.devN
.Looking at the code listed in the traceback, it looks like the tool would also choke on any build IDs that were included, though I expect creating a tag with that information would be weird.
I do think that tags with pre-release IDs on them are common enough that I would expect these to work.
The text was updated successfully, but these errors were encountered: