README.md file example need to updated gives `attributeError: module 'semver' has no attribute 'Version'`

[slayer321]

README.md file example need to updated gives `attributeError: module 'semver' has no attribute 'Version'`

[tomschr]

No problem. Thanks for your contribution anyway. If you observe anything else, don't hesitate and open a issue.

[spoorcc]

Thanks for the reply @tomschr!

I'm already a big fan of your package 😉! I use it in https://github.com/dfetch-org/dfetch.

In my case a sub-sub dev-dependency started using poetry-semver unfortunately 😢. This caused pylint to start complaining which brought me to this issue. prospector --> requirements-detector --> poetry-semver

I've opened an issue in the requirements-detector repository to replace poetry-semver with semver (landscapeio/requirements-detector#40) maybe I can create a new fan 😉.

[tomschr]

Thanks Ben/@spoorcc! Oh, that's really nice, thank you!

Ahh yes, naming things can be really tricky. I'm sorry for your issues. I thought about renaming the package, but wasn't sure if that wouldn't cause more problems than it solved.

Thanks for opening the new issue. 👍 Hope they can migrate it to this project. 😉

All the best and if you have further ideas, comments, bug fixes etc. let us know.

[tomschr]

Thanks @slayer321 for your report and welcome! 👋

I'm not sure if I understand your issue. The current master branch contains the development version of this project (currently 2.0.0-dev.3).

The class VersionInfo was the old name; it has been renamed to Version. Regardless of the name change, there is still an alias VersionInfo available.

Here is a small session that use both:

$ PYTHONPATH=src python3 -c "import semver; print(semver.VersionInfo.parse('1.2.3-pre.2+build.4'))"
1.2.3-pre.2+build.4
$ PYTHONPATH=src python3 -c "import semver; print(semver.Version.parse('1.2.3-pre.2+build.4'))"
1.2.3-pre.2+build.4

Can you elaborate? 🙂 Are you still using the old version 2? That change will be introduced in semver v3.

[slayer321]

yes, I check I'm still using semver 2 .. Will close this issue

[spoorcc]

For whomever it may be useful, I ran into a similar issue, but this was due to a package bringing in poetry-semver . This is also called semver and had me scratching my head for a while before figuring out.

[tomschr]

For whomever it may be useful, I ran into a similar issue, but this was due to a package bringing in poetry-semver . This is also called semver and had me scratching my head for a while before figuring out.

Thanks for the comment @spoorcc! We have the similar issue #259. Unfortunately, the name "semver" is very common. I'm not sure how to solve this as PyPI allows libraries of the same name.

Regarding the python-semver: the GitHub project is archived. It seems, it was done as the project isn't maintained anymore. The last commit was 3 years ago. Maybe a good opportunity to migrate to this project? 😉