On 1 May 2011 15:33, Mateusz Harasymczuk <m...@harasymczuk.pl> wrote: > I have to agree with this guy: > http://code.djangoproject.com/ticket/5446
There are two competing third-party solutions to a country-field out there, both helpfully named django-countries: 1) http://code.google.com/p/django-countries/ 2) https://bitbucket.org/smileychris/django-countries/ No. #1 uses a country model, a foreign-key to this model is then a "country"-field. No. #2 has the countries in a tuple and a proper CountryField. The former is the first hit on google and it is easy to change the list of countries, in the latter you need one fewer JOIN. The latter is also more used, and is the only one on pypi and djangopackages. The keys of the model used in #1 is compatible with the values of #2 but of course the allowed values differ. We could just pick one of these. HM -- 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.
