Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

pep440 style and tagged version question

See original GitHub issue

Is this normal that for exact tagged version when distance == 0 I have TAG+DISTANCE.gHEX.dirty version and not just TAG version ?

Without change form if pieces["distance"] or pieces["dirty"]: to if pieces["distance"]: I do not know how to create stable final packages.

Issue Analytics

State:
Created 8 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

warnercommented, Jun 27, 2015

If you have distance==0 and dirty==False, then you should get just TAG: that’s how to create stable final packages.

If you have distance==0 and dirty==True, then yeah, you should at least get the .dirty suffix. Final packages should be built from tagged and non-dirty trees. Does your build process modify source code just before making a release? Is there a way to change your build process to not do that?

I guess we don’t strictly need to add +DISTANGE.gHEX too… the .dirty marker is probably sufficient warning that a bug report is running from modified source (and therefore you, as the maintainer/triager, have no idea what exact they were running). But it does make it more clear that something unusual is going on.

What build process are you using? The standard setup.py install / setup.py sdist processes are supposed to modify the _version.py in the build/ directory, not the source directory, so they shouldn’t cause a “dirty” tree. There was an older version that didn’t do this correctly (in particular when doing e.g. setup.py sdist register upload), but I thought we’d fixed that.

If you do a “final build”, and then do a “git status”, what does it report as being modified?

0reactions

warnercommented, Jun 30, 2015

Ok, great. Feel free to file a new issue if the problem shows up again.

Top Results From Across the Web

pep440 style and tagged version question · Issue #85 - GitHub

Is this normal that for exact tagged version when distance == 0 I have TAG+DISTANCE.gHEX.dirty version and not just TAG version ?

PEP 440 – Version Identification and Dependency Specification

Abstract. This PEP describes a scheme for identifying versions of Python software distributions, and declaring dependencies on particular versions. This ...

How to use PEP440 beta tags with setuptools_scm?

Is there a way to use PEP440-style beta release tags, such as v0.1.3b0 with setuptools_scm? It currently gives an error invalid literal for ......

versioneer module — PyGraphistry 0.11.8+0.g7edbc22.dirty ...

style : the style of version string to be produced. See “Styles” below for details. Defaults to “pep440”, which looks like TAG[+DISTANCE.

Versioning - Renovate Docs

Docker images don't really have versions, instead they have "tags". ... SemVer -style versions allowed in pyproject.toml to the PEP440 representations used ...