Activity

1. tomschr

   added

   Release_3.x.yOnly for the major release 3Only for the major release 3

   on Nov 5, 2020
2. tomschr

   self-assigned this

   on Nov 5, 2020
3. josefkorbel commented on Jul 28, 2021

   

   josefkorbel

   on Jul 28, 2021

   Last edited by josefkorbel

   More actions

   I've just found this issue while dealing with development pypi packages versioning, so I read PEP440 (https://www.python.org/dev/peps/pep-0440/) and according to that the semantic version of 3.0.0-dev.2 is actually not valid if I am not mistaken, as it should be 3.0-dev2.
4. tomschr commented on Jul 30, 2021

   

   tomschr

   on Jul 30, 2021

   MemberAuthor

   More actions

   Thanks Josef, much appreciated your report.

   Well, seems semver and PEP440 are only partly compatible. Semver allows to define a patch part, whereas PEP440 does not. There are different approaches in the wild how to deal with version information.

   Apart from that, PEP440 has been assigned the type "Informational". According to PEP001, this type is defined as (emphasize by me):

   "An Informational PEP describes a Python design issue, or provides general guidelines or information to the Python community, but does not propose a new feature. Informational PEPs do not necessarily represent a Python community consensus or recommendation, so users and implementors are free to ignore Informational PEPs or follow their advice."

   A lot of libraries do that and follow a different approach. 😉

   For this reason, I would tend to follow what's written in the description.
5. tomschr

   added a commit that references this issue on Jan 20, 2022

   Fix python-semver#315: Create 3.0.0-dev.3

   ...

   This issue will close once commit 221bfba is merged into the 'master' branch.

   221bfba
6. tomschr

   linked a pull request that will close this issueRelease/3.0.0 dev.3 #348on Jan 20, 2022
7. tomschr

   closed this as completedin #348on Jan 20, 2022