Semver breaks on additional installation of conan and artifactory

[dnns92]

Semver breaks on additional installation of conan and artifactory

[alexandrevicenzi]

The package node-semver was already renamed, see podhmo/python-node-semver#39.

It will be in 0.9.0 release, see podhmo/python-node-semver#45.

Conan will need to update their dependency to not clash with this package.

[dnns92]

This is related to node-semver, a dependecy of conan. Therefore, one will never be able to run conan and this package in the same venv. I dont want to stick my nose into stuff I don't know enough about, but there are a couple of packages named semver, like also the one named here: #381. Maybe calling this package python_semver or similar is more future-proof.

[tomschr]

Thanks @dnns92 for your report, much appreciated.

I've tried to replicate it and it looks like it's issue #259. It's a name clash.

If you list your packages you get:

$ pip list
node-semver        0.6.1
[...]
semver             2.13.0

If you look closer in your Python environment, you will see these files and directories:

$ ls -ld .env/lib/python3.10/site-packages/semver*
.env/lib/python3.10/site-packages/semver
.env/lib/python3.10/site-packages/semver-2.13.0.dist-info
.env/lib/python3.10/site-packages/semver.py

In other words, there is a file semver.py which comes from this project. But at the same time, there is a directory semver which comes from the node-semver project. It seems, the latter takes precedence over the former. That's why you see this error as the node-semver doesn't provide a VersionInfo class.

Unfortunately, PyPI does not prevent from uploading a project which contains an already existing module/package of the same name.

I fear, this is something hard to solve (if at all). Renaming this project would break a lot of existing projects. If you know an idea to solve this, I'm open for your suggestion.

At the moment, semver and node-semver cannot coexist in the same Python environment. As such they cannot be used at the same time.

[tomschr]

Maybe calling this package python_semver or similar is more future-proof.

Thanks, that's what I also though about, but I think it would be a bad idea.

Renaming this project will break a lot of existing projects that depends on semver. According to the semver's dependency list, there are over >23.500 repositories(!) that uses this project.

Whereas at the same time node-semver's dependencies lists >800 repos.

Forcing all 23.500 maintainers to use a different name would have a huge impact and wouldn't make these project maintainers very happy. Even if we file issues to notify of the rename, it's unrealistic and a huge task.

I'm not even sure, if we can demand a rename from the node-semver project (although the impact would be less than for this project).

So, not sure how to handle this... 🤷

[tomschr]

@dnns92 Thanks for all your comments.

I've looked a bit closer and it seems the other project is already aware of this problem and has issue podhmo/python-node-semver#39. Additionally they work on a new release, see podhmo/python-node-semver#45. Unfortunately, it's not yet released.

To solve this is to use the new name nodesemver instead of semver once they released it.

Maybe ask in the python-node-semver project when they will release the new version?

[tomschr]

In the light of a new release for python-node-semver, I think this project can't do much. There is already a solution work in progress, although not yet released.

As such, I think it doesn't make sense to have this issue open. Closing it for the time being.

Many thanks for your contribution!