#30538: Inconsistent slug generation behaviour of slugify() and prepopulated 
fields
in Django Admin.
-------------------------------------+-------------------------------------
     Reporter:  Loo Zheng Yuan       |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  Utilities            |                  Version:  master
     Severity:  Normal               |               Resolution:  wontfix
     Keywords:  slugify              |             Triage Stage:
  prepopulated fields                |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by felixxm):

 * status:  new => closed
 * type:  Uncategorized => Bug
 * component:  Uncategorized => Utilities
 * version:  2.2 => master
 * resolution:   => wontfix


Comment:

 Thanks for this report. `slugify()` and `URLify` behave differently since
 their introduction in dd5320d1d56ca7603747dd68871e72eee99d9e67 and
 ed114e15106192b22ebb78ef5bf5bce72b419d13 in 2005. Changing this behavior
 would be backward incompatible, that's why I'm marking this as "wontfix"
 (see [https://docs.djangoproject.com/en/stable/internals/contributing
 /triaging-tickets/#closing-tickets follow triaging guidelines]). Please
 see
 [https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!searchin
 /django-developers/urlify|sort:date/django-
 developers/X2JZV7cMtD4/m8gtBmixXcsJ an old thread on the django-
 developers]. You can leave your comment there if you think that this
 behavior should be changed.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30538#comment:1>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.6f3709b0eb875705d7e8b99bc25aade8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to