Red Hat Bugzilla – Bug 1298644
Please provide python3-slugify
Last modified: 2016-01-17 20:48:31 EST
python-slugify support python3, as such we should also ship python3 support. Please enable it for the RPM using the following
Ugh, this RPM is not https://pypi.python.org/pypi/python-slugify. Hmm, is there a specific reason you didn't use this version, which is more mature then the one you packaged?
python-frappe requires the older slugify to run.
And for the momment frappe developers do not have plans to move to python3.
I will ask to the packaging mailing list about this to libs packaging.
Thanks for the fast reply, I also sent you a private email, which just extends some of the topic here. Just a heads up.
I will look into python-frappe and see how they are using it.
For the record:
I will wait some comment upstream but looks like I can retire python-slugify is frappe do not need any more.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Note that the slugify in PyPI is not the same than python-slugify.
These are not the same source, so I cannot update the old slugify. It would make sense to retire this package in Rawhide as nothing requires it and make room for the new python-slugify.
Another solution would be to package the new PyPI's python-slugify as python-python-slugify (a legit name as per our Package Naming Guidelines), but that would only make things confusing and there is no need to keep the old slugify.
Are they more or less equivalent? If yes, I'd just switch to the other sources after reviewing them for license compatibility. After all, if this one is retired and a package with an identical name is added, for the user it's exactly the same as if the sources were switched. For the packagers it's less work.
Building in Rawhide: http://koji.fedoraproject.org/koji/taskinfo?taskID=12588750
Sorry, this is the actual build: http://koji.fedoraproject.org/koji/taskinfo?taskID=12588760