Opened 13 years ago
Closed 12 years ago
#17136 closed Cleanup/optimization (wontfix)
Localflavor inconsistencies
Reported by: | Jonathan Liuti | Owned by: | Jonathan Liuti |
---|---|---|---|
Component: | contrib.localflavor | Version: | 1.3 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
I think the localflavor module could be improved by using some api standards.
eg:Be Localflavor is missing a proper BERegionSelectField and BEProvinceSelectField but CA has it's own.
Which leads me to dig into the source code to understand how to make it work.
This is not what people would expect from such an awesome framework as Django.
I think this could be easily corrected and I'd be glad to help if this ticket is validated.
Change History (4)
comment:1 by , 13 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 13 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
I will post to the google group mailing asap. Thx for the fast feedback btw.
comment:3 by , 12 years ago
Ramiro, what sort of improvements did you have in mind when you accepted the ticket?
comment:4 by , 12 years ago
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
I think this ticket does not contain any concrete proposal. Closing now that localflavors are going to have their own repository.
Localflavor functionality is provided and enhanced with contributions from users that live in the respective countries/geographical regions.
So, if you are proposing to submit more form field/widgets that you think/know would be of help to people creating web apps targeted to users from such country then you are welcome to do so. It could also be a good idea to subscribe yourself to the django-i18n mailing list and post there announcing your intentions and/or to seek help/opinion with a local Django user community if any.