setuptools_scm: Built wheel is invalid: Metadata 1.2 mandates PEP 440 version, but '0.0.2.dev1.post1.dev2-g8fd2842' is not
Attempting to run tox tests on a library I am building is throwing the below error:
Processing ./.tox/.tmp/package/1/python-step-series-0.0.2.dev1.post1.dev2-g8fd2842.tar.gz
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing wheel metadata: started
Preparing wheel metadata: finished with status 'done'
Building wheels for collected packages: python-step-series
Building wheel for python-step-series (PEP 517): started
Building wheel for python-step-series (PEP 517): finished with status 'done'
Created wheel for python-step-series: filename=python_step_series-0.0.2.dev1.post1.dev2_g8fd2842-py3-none-any.whl size=18021 sha256=7c172e5d554075b0c12255e06be171c067edf4569bb621c5fa573070d39d581d
Stored in directory: /home/user/.cache/pip/wheels/d1/5f/e0/84fd855c772a59469c7065c94464233a7532667a9c94430803
WARNING: Built wheel for python-step-series is invalid: Metadata 1.2 mandates PEP 440 version, but '0.0.2.dev1.post1.dev2-g8fd2842' is not
Failed to build python-step-series
ERROR: Could not build wheels for python-step-series which use PEP 517 and cannot be installed directly
I believe it is being caused by the warning I’ve titled this issue with.
I just started getting this error this morning and am completely stuck on why I am all of a sudden seeing it. I looked at #278 as it seemed similar, but was not. Regardless, as like in that issue, here are the outputs for git tag, git describe and git status:
git tag:
0.0.2dev0
0.0.2dev1
v0.0.1
git describe:
0.0.2dev0-6-g8fd2842
git status:
On branch 0.0.2
Your branch is up to date with 'origin/0.0.2'.
nothing to commit, working tree clean
Curiously, creating a new tag (i.e. 0.0.2dev2) will allow me to run the tests until my working tree gets dirty again, so creating a new tag every time I want to test isn’t viable nor proper.
I am 100% stuck, so please let me know what I can do to rectify this if you are able. Jules
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 22 (14 by maintainers)
the next release will error out on those invalid tags
resolved with the 6.4.0 release
I absolutely agree that a call can massively speed up the discussion, I still want a extra issue to record the details /conclusion
@RonnyPfannschmidt We default to
no-guess-devsince for me it’s the only sane default. Can you really ever guess the next version right? After version 1.3.2 could come 1.3.3 or 1.4 or even 2.0, right? Sono-guess-devfeels more deterministic using the .post1.devN trick. CC @abravalheri