Hi Adrian, Thanks for taking the lead on this! I reviewed related tickets in Trac and I have a few suggestions.
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. 2) There's a dozen Trac tickets for adding new countries: Bulgaria, Nicaragua, Hungary, Malaysia, Venezuela, South Korea, Bangladesh, New Zealand, Guatemala, Latvia, Iran, Singapore. Would it make sense to create these local flavors now — maybe after asking the community to update the patches if they aren't ready? 3) I'd like to see some guidelines on what features a local flavor is expected to provide. Two examples: - Are model fields that just inherit TextField and set a particular form_class useful? (#10087) - Are pluralization template filters a good idea? (#17632) I believe it's a good thing for the Django community to maintaining some consistency among local flavors. Since we plan to defer to local maintainers in each country, we should document the expectations and best practices. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
