It feels to me more like an option to SlugField and I feel UnicodeSlugField is a bit ugly. If however we find an example where Michael's point is valid (an external 3rd party backend which uses ascii chars for SlugField now) then we should go with that.
On 5 November 2014 03:20, Michael Manfre <mman...@gmail.com> wrote: > Should the unicode validated field (either options) have a different > internal type for the sake of 3rd party database backends? I'm not sure if > any currently store SlugFIeld in an ascii char datatype and would need an > easy way to differentiate. > > Regards, > Michael Manfre > > On Tue, Nov 4, 2014 at 8:27 PM, Tim Graham <timogra...@gmail.com> wrote: > >> I wanted to solicit feedback on the two approaches to supporting unicode >> in SlugField: >> >> 1. Added a unicode argument to models.SlugField and forms.SlugField. >> https://github.com/django/django/pull/1979 >> >> 2. Added models.UnicodeSlugField and forms.UnicodeSlugField. >> https://github.com/django/django/pull/1987 >> >> The patch author says, "On one hand, I like the new field approach >> because it gives us an easier upgrade path. On the other hand, it feels >> like I'm polluting django.db.models and django.forms with slightly >> different versions of something that's already there." >> >> Approach 1 does seem cleaner to me, but I'd be interested in hearing from >> those interested in this feature. >> >> Ticket: https://code.djangoproject.com/ticket/16501 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-developers+unsubscr...@googlegroups.com. >> To post to this group, send email to django-developers@googlegroups.com. >> Visit this group at http://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/33e9747f-6ced-4710-9e59-ca128e065c5c%40googlegroups.com >> <https://groups.google.com/d/msgid/django-developers/33e9747f-6ced-4710-9e59-ca128e065c5c%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAGdCwBv%3DfGD-DpG4w9Bd3_9FkcKiw_CYqhR8tJK8W1EC_zvQNg%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAGdCwBv%3DfGD-DpG4w9Bd3_9FkcKiw_CYqhR8tJK8W1EC_zvQNg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMwjO1H%2BCUXs%2B8_fQ_xiAMu%3DR%2BAxMNMmaTwaAEkavOmtAPcy8w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
