#10335: tzinfo.py should use getdefaultencoding instead of getdefaultlocale[1]
-------------------------------------+--------------------------------------
          Reporter:  gthb            |         Owner:  nobody                   
                              
            Status:  new             |     Milestone:                           
                              
         Component:  Core framework  |       Version:  1.0                      
                              
        Resolution:                  |      Keywords:  locale encoding 
getdefaultlocale getdefaultencoding mac
             Stage:  Unreviewed      |     Has_patch:  1                        
                              
        Needs_docs:  0               |   Needs_tests:  0                        
                              
Needs_better_patch:  0               |  
-------------------------------------+--------------------------------------
Comment (by gthb):

 Just found this, for what it's worth, in
 http://bugs.python.org/issue813449 :

 ''This is a known limitation: getdefaultlocale should not be used in new
 code.

 If the intention is to compute the locale's encoding,
 locale.getpreferredencoding should be used instead.''

 Still, no such warning is given in http://www.python.org/doc/2.5/lib
 /module-locale.html

 In any case, locale.getpreferredencoding also just returns
 _locale._getdefaultlocale()[1] on darwin or mac, so switching to that will
 not resolve this issue.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/10335#comment:2>
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