question-mark
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.

Prepare semver 3.0.0

See original GitHub issue

Situation

As we have released 2.9.0 of semver, we should consider of moving to 3.0.0 soon. This is needed to start working on adding new features and optimizing source code for Python 3.

(I’ve created this issue to make the upcoming 3.0.0 more visible and to have a record when we need to search the history.)

Suggested Solution

In order to create semver 3.0.0, we need to think about the following tasks:

  • Create a maintenance branch for 2.x.y line: maint/v2
  • Remove test target py27 and py34 from tox.ini
  • Tag the 2.9.0 release.
  • Update the Trove classifiers in setup.py and remove support for Python 2.7 and 3.4.
  • Optimize source code for Python 3 only and remove any code that was introduced due to 2.7.
  • Provide (and label it correctly) the 2.9.0 documentation for ReadTheDocs. We need a configuration that should be possible that old (2.9.x) and new versions (3.*) are still available and can coexit together peacefully. 😉
  • Change version number in master to 3.0.0.

Anything else? 😉

I’ve updated the description in https://github.com/k-bx/python-semver/issues/161#issuecomment-539045512 of issue #161

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
tlaferrierecommented, Oct 17, 2020

I have just read that python 3.5 has reached end of life. I think we should go ahead and focus on supporting python >= 3.6 since there are quite a few features relating to type hints that could be useful to us that were only added in 3.6.

0reactions
tomschrcommented, Oct 17, 2020

Good catch! Thanks for the hint! I’ve updated setup.py and tox.ini accordingly.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Semver 3.0.0-dev.3 – Semantic Versioning — python-semver ...
PATCH version when you make backwards compatible bug fixes. Additional labels for pre-release and build metadata are supported. To import this library, use:...
Read more >
Semantic Versioning 2.0.0 | Semantic Versioning
Summary. Given a version number MAJOR.MINOR.PATCH, increment the: MAJOR version when you make incompatible API changes; MINOR version when you ...
Read more >
semver - npm
The semantic version parser used by npm.. Latest version: 7.3.7, last published: 5 months ago. Start using semver in your project by running ......
Read more >
Linux/Python Compatible Semantic Versioning 3.0.0
This is a fork of Semantic Versioning 2.0. The specific changes have to do with the format of pre-release and build labels, specifically...
Read more >
SemVer v3 Released - Code Engineered
SemVer v3 is release. ... This is version 3.0.0. ... would become dep started there was a desire to make changes to the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found