You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
Since
python-ulid
ulid
ulid
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:
The text was updated successfully, but these errors were encountered: