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

Conflict with python-slugify #27

Open
sdhutchins opened this issue Dec 6, 2017 · 2 comments
Open

Conflict with python-slugify #27

sdhutchins opened this issue Dec 6, 2017 · 2 comments

Comments

@sdhutchins
Copy link

sdhutchins commented Dec 6, 2017

Both this project and python-slugify (which logzero uses as a dependency) have the root module as slugify which I'm guessing a lot of users have experienced. I like this package, but I think it'd help to rename the root folder something like UnicodeSlugify or unicodeslugify.

Just a thought...

@Natim
Copy link

Natim commented Dec 10, 2018

What about unicode_slugify?

@dbrgn
Copy link

dbrgn commented Feb 4, 2020

I also ran into this problem. On Arch Linux, python-slugify is provided as an official package, used for example by home assistant or by transifex-client.

On the other hand, python-unicode-slugify is packaged in the AUR and required by tools like opensnitch.

Unfortunately the name conflict means that I cannot install transifex-client and opensnitch on my system at the same time.

Please consider renaming the top level module to unicode_slugify and releasing a new major version. I know it's a breaking change, but the convention is to have a module name that matches the project name.

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

3 participants