Repository navigation
Name conflict with other slugify package #81
Description
When working on the following code:
from slugify import slugify
fname = slugify("cc / loc") + ".png"My IDE (PyCharm 2018.2.5) will suggest to automatically download a package, but the wrong one. And this results in an error: NameError: name 'unicode' is not defined
The namespace of this package should be changed, or the half implemented package should be removed from PIP.
A tool like this should work out of the box.
Activity
[-]NameError: name 'unicode' is not defined[/-][+]Name conflict with other slugify package[/+]un33k commentedon Jul 27, 2019
I don't think the name-space
python-slugifycan have multiple versions on pypi. With that said, some people, sadly, clone the repo and publish it aspython-slugify2,python-slugify3etc. If your IDE falls for the number in the name as the trueversionand installs the latest version, then it is possible that a fake/clone version is installed by PyCharm.You can be more specific and install it as
python-slugify[unidecode]as per https://github.com/un33k/python-slugify#noticeroniemartinez commentedon Jul 27, 2019
He installed the slugify package, not
python-slugify. It's been there 9 years ago, certainly not a clone.https://github.com/zacharyvoase/slugify/blob/master/src/slugify.py#L24
un33k commentedon Jul 27, 2019
@EmileSonneveld Only you know what you installed. Any package should install its own dependencies or fall on a default one, and provide options. Never used pyCharm so I don't know what it does. See what you installed and raise a ticket with that package instead.
roniemartinez commentedon Jul 27, 2019
@un33k I use PyCharm. If you import a module and it does not exist yet PyCharm will ask you to install what you imported, in the case of:
import slugifyIt will install the
slugifypackage and notpython-slugifyun33k commentedon Jul 28, 2019
@roniemartinez then this issue needs to be posted on the slugify's page instead.
EmileSonneveld commentedon Jul 28, 2019
I raised the issue in the conflicting library too. However, I am convinced that if this package is called
python-slugify, the namespace in the code should reflect that. However, it is difficult to fix that while retaining backwards compatibility of course.un33k commentedon Jul 28, 2019
@EmileSonneveld name of a package is different than the set of api it publishes.
python-slugifyis a reserved name for pypi. Remember that importing sys in python isimport sysand notimport python-sys. So name of a package has nothing to do with what is inside of it.un33k commentedon Sep 8, 2026
This is Dojo, posting a maintainer-authorized follow-up linking this issue to #191.
Install-name versus import-name troubleshooting is documented. No package namespace rename is introduced.
The default algorithm remains legacy; improved output rules are opt-in. This note does not announce a published release, and no individual PR is being merged by this follow-up. Thank you for the contribution and discussion.
🚀 Generated with Dojo ⛩️