Hi Aymeric & Adrian, I didn't see any further discussion or consensus on the issue of the generic localflavor. The 1.5 docs and (accelerated) deprecation of localflavor are a little hazy regarding the generic localflavor.
The 1.5 docs say that it hasn't been removed (yet), but doesn't say it will remain where it is, or move into core, or simply disappear with no equivalent external package. The docs also said that (all of) `django.contrib.localflavor` would be removed, and any import below `django.contrib.localflavor` currently raises a warning with a message to use `django-localflavor-*` packages instead. But for generic, there is none. So as it stands, anyone who uses `django.contrib.localflavor.generic` (all my projects do) will find that it has been removed in 1.6 with no equivalent in core and no equivalent external package. I would prefer to see these reinstated in django core for 1.6, and the 1.5.x docs updated with an explanation on where they can be imported from when upgrading to 1.6. It's probably a bit much to ask for the non-biased international format fields to become the defaults, but I would definitely like to see these move into core before `django.contrib.localflavor` goes away. It would seem a bit silly to me to create an external `django-localflavor-generic` package with 3 international (not locale specific) format fields and no other localisation. Django has always had great international support in core, and I doubt these three fields are much of a burden to maintain. Also, as a separate issue I noticed that only a handful of the `django-localflavor-*` packages are on PyPI. This makes the method inconsistent and potentially more difficult (depending on your locale) to add them as requirements to a project. Cheers. Tai. On Tuesday, 16 October 2012 07:17:43 UTC+11, Aymeric Augustin wrote: > > > 1) Can we move the fields defined in > django.contrib.localflavor.generic.forms to django.forms? > > Currently the US-biased fields are in django.forms and the non-biased ones > in django.contrib.localflavor.generic.forms — an interesting perspective :) > > The alternative is to deprecate them entirely. > -- You received this message because you are subscribed to the Google Groups "Django developers" 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
