-
Notifications
You must be signed in to change notification settings - Fork 8
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.
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
Project name mismatch: here ity is called "pywindow" and on PyPI it is called "pywindowx" #3
Comments
I believe the issue is that there already a pywindow on pypi. The name was therefore taken so pywindowx was chosen a substitute. I think the best thing to do is document this in a visible place, like the readme or something. But a better alternative is not apparent to me. By packages on various systems do you mean conda vs pypi for example? |
No, on different systems like Redhat, FreeBSD, Arch, Gentoo. For example, the list of packages for NWChem for different systems: https://repology.org/metapackage/nwchem/versions. |
Practically speaking, Conda and PyPI isn't a good way to install software, because they are Python-specific, only cover some OSes, and not others, and are potentially insecure because they don't verify file fingerprints. Systems (OSes) create ports/packages for software projects. Package manager is the right way to install software in general. |
If I'm understanding this correcly, the issue is that when someone wants the create a distro package - they may choose to use "pywindow" based on the name on github or "pywindowx" based on the pypi name. Do you have a propsed solution to this? I don't know what can be done about this. |
Yes, this is the issue. There is a name clash. These 2 packages can't be installed at the same time, because the real name is There is no solution short of renaming. |
I was going to create the FreeBSD port, but I am not sure what name should it have. |
Ok, thank you, understood. Ultimately this is up to @marcinmiklitz but I think renaming this project is unlikely because there is a published paper referencing it as pywindow, which also points to this url. |
Then you should add a notice in large letters, both here and on PyPI, recommending what the package name should be (or is desired), the reasons (that you just mentioned), etc. This would prevent confusion as much as possible in this situation. |
https://pypi.org/project/pywindowx/
When packages are created for various systems, this would cause confusion, and some packages will be named "pywindow" and others - "pywindowx".
The text was updated successfully, but these errors were encountered: