concentricsky/django-basic-models — pull request #7 by auzigog (2012-06-26 17:16:20+00:00)
Title: Switch slugify to built in filter

The u_slugify function does handle some unicode cases better. For most sites, I think it isn't necessary, though. And in this pull request, I've removed it because it produces inconsistent results when used with the admin. The admin slug field set to "prepopulate" uses a slugify() implementation (in javascript, of course).

Given "Foo Bar",

slugify would ouput "foo-bar"

and u_slugify would output "Foo_Bar"

If some models are created programmatically and some are created with the admin, this would lead to inconsistent slugs and inconsistent URLs.

I think that if folks need advanced unicode support, they should implement it on a per-site basis, and that using slugify() works for most cases.