Skip to content

Create semver 3.0.0-dev3 #315

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
2 of 4 tasks
tomschr opened this issue Nov 5, 2020 · 2 comments · Fixed by #348
Closed
2 of 4 tasks

Create semver 3.0.0-dev3 #315

tomschr opened this issue Nov 5, 2020 · 2 comments · Fixed by #348
Assignees
@tomschr
Labels
Release_3.x.y Only for the major release 3

Comments

@tomschr
Copy link
Member

tomschr commented Nov 5, 2020 •
edited
Loading

Situation

As 3.0.0-dev.2 was just released, we should think about to coordinate the next development release.

Suggested Plan

Some ideas for this release:
@tomschr tomschr added the Release_3.x.y Only for the major release 3 label Nov 5, 2020
@tomschr tomschr self-assigned this Nov 5, 2020
@josefkorbel
Copy link

josefkorbel commented Jul 28, 2021 •
edited
Loading

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.

@tomschr
Copy link
Member Author

tomschr commented Jul 30, 2021

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.

tomschr added a commit to tomschr/python-semver that referenced this issue Jan 20, 2022
@tomschr
Fix python-semver#315: Create 3.0.0-dev.3
221bfba 
* Improve entries for PyPI in setup.cfg
  * Remove key "download_url" as it points to a broken URL
  * Add Changelog entry pointing to RTD
* Raise version to 3.0.0-dev.3
* Update release procedure
* Update Black formatter config
  * Replace "exclude" with "extend-exclude"
  * Ignore all *.py files in project's root directory
  * Include "setup.py" explicity
@tomschr tomschr linked a pull request Jan 20, 2022 that will close this issue
Release/3.0.0 dev.3 #348
Merged
@tomschr tomschr mentioned this issue Jan 20, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tomschr tomschr

Labels
Release_3.x.y Only for the major release 3
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Release/3.0.0 dev.3 tomschr/python-semver
2 participants
@tomschr @josefkorbel