#16501: validators.py don't like unicode slug
-------------------------------+------------------------------------
Reporter: norn | Owner: pbnan
Type: New feature | Status: reopened
Component: Core (Other) | Version: 1.3
Severity: Normal | Resolution:
Keywords: unicode, slug | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Changes (by PaulM):
* stage: Ready for checkin => Accepted
Comment:
I'm bumping this back out of RFC. While I agree wholeheartedly that we
need to allow users to choose unicode slugs if they so desire, we can't
just arbitrarily change the way this works. Many developers depend on the
promise that the slug is ASCII. Arbitrarily switching to allow unicode
characters will produce bugs in previously stable code, and may introduce
security vulnerabilities.
Django's backwards compatibility policy requires that features like this
continue to work as documented. Before this patch is ready to commit, the
patch must be re-worked so that the default slug behavior of reducing to
ASCII remains. Whether or not the default behavior should change at some
point in the future (1.5 or 1.6) is a matter that should be discussed on
the django-dev list.
--
Ticket URL: <https://code.djangoproject.com/ticket/16501#comment:12>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
