Skip to content
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

Possible confusion with the “ulid” package #13

Open
musicinmybrain opened this issue Jan 30, 2024 · 1 comment
Open

Possible confusion with the “ulid” package #13

musicinmybrain opened this issue Jan 30, 2024 · 1 comment

Comments

@musicinmybrain
Copy link
Contributor

Since

there is the possibility of user confusion.

Is there a possibility of finding a truly unique name for this library in order to reduce the possibility of confusion?

The Fedora Linux packaging guidelines say:

If the importable module name and the project name do not match, users frequently end up confused. In this case, packagers SHOULD ensure that upstream is aware of the problem and (especially for new packages where renaming is feasible) strive to get the package renamed. The Python SIG is available for assistance.

@mdomke
Copy link
Owner

mdomke commented Mar 19, 2024

You're of course right that there is another package with the same importable name, but it seems to be abandoned anyway (at least the last commit is 7 years old). I also think that it is pretty unlikely that somebody will use both packages at the same time, resulting in a conflict of importable packages. It might have been a mistake though at the time to choose the same package name as an already existing project, but I'm kinda against changing it now if there is not an actual problem. I can however try to clarify this problem in the README.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants