tickets: 8276
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 8276 | 2008-08-13 02:42:15 | 2011-09-28 16:12:17 | 2022-03-06 03:41:49.524817 | Accepted | closed | contrib.localflavor | Uncategorized | Normal | dev | fixed | Change fields' names in django.contrib.localflavor.pl.forms | I would like to propose backward incompatible change {{{django.contrib.localflavor.pl.forms}}}: Some classes present in {{{django.contrib.localflavor.pl.forms}}} are named in a werid way - they are neither short and useful, nor offical translations of corresponding numbers. ||Old name||New name|| ||`PLNationalIdentificationNumberField`||`PLPESELField`|| ||`PLTaxNumberField`||`PLNIPField`|| ||`PLNationalBusinessRegisterField`||`PLREGONField`|| ||`PLVoivodeshipSelect`||`PLProvinceSelect`|| ||`PLAdministrativeUnitSelect`||`PLCountiesSelect`|| Not only Polish people in everyday language use those acronyms, but even Polish officials refer to those numbers as `PESEL`, `REGON` and `NIP`: * http://www.mswia.gov.pl/portal/en/1/383/18102007_Meeting_of_G6_Ministers__Invitation_for_Conference.html * http://www.stat.gov.pl/bip/regon_ENG_HTML.htm I'm willing to prepare the patch if those changes are accepted. | nobody | Piotr Lewandowski <django@icomputing.pl> | 0 | 1 | 0 | 0 | 0 | 0 |