tickets: 8323
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 8323 | 2008-08-14 19:31:07 | 2011-01-18 23:20:32 | 2022-03-06 03:41:56.985519 | Design decision needed | closed | contrib.localflavor | dev | duplicate | British local flavor package named inconsistently | I just noticed that according to the [http://www.djangoproject.com/documentation/localflavor/ local flavor documentation], the packages are named using the [http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm ISO 3166 country codes]. However, at present, the British local flavor is within a package called "uk" (United Kingdom) rather than "gb" (Great Britain), which would seem to be the correct 2 letter code. This is a pretty minor issue as no other country has been assigned "uk" as a country code at this time. For consistency, we may want to rename the package to "gb". If so, this should probably be done prior to 1.0 to avoid compatibility issues in the future. If it is decided that the name should be left as is, then I think the documentation should at least be updated to mention this legacy naming anomaly. All the other local flavors appear to be using the correct ISO codes. | nobody | frasern | 0 | 0 | 0 | 0 | 0 | 0 |