#10456: Canada localflavor improvements/fixes
-------------------------------------------------+--------------------------
          Reporter:  mmulley                     |         Owner:  nobody       
 
            Status:  new                         |     Milestone:               
 
         Component:  django.contrib.localflavor  |       Version:  SVN          
 
        Resolution:                              |      Keywords:  localflavor 
ca
             Stage:  Accepted                    |     Has_patch:  1            
 
        Needs_docs:  0                           |   Needs_tests:  0            
 
Needs_better_patch:  1                           |  
-------------------------------------------------+--------------------------
Changes (by mtredinnick):

  * needs_better_patch:  => 1
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 The data value used in the choices list that is destined to be stored in
 the database is not a difficult issue at all: it's not used for user-
 displayable data. If somebody is using it for that, then they're using it
 incorrectly. The first element in those tuples are simply the database
 storage values. They could be integers or anything. So let's leave that
 portion in the previous ticket, but it will almost certainly be wontfixed,
 since breaking existing database data is bad.

 Please create a patch without the duplication from #10365, so that we can
 deal with the improvements here in isolation.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/10456#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to