| Issue 9: | find some way to get the Calendar class to initialize itself from the current locale | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
Currently the Calendar class initializes itself to the default Constants class locale (which initializes itself to en_US if not told otherwise). This means that if parsedatetime is started in a locale that isn't en_US the Calendar object will be set to en_US. Question is this: should Calendar change to have a flag that is passed to Constants() init routine or update the docs to point out the issue so the caller knows if they want something other than en_US they have to set it up. |
||||||||||
,
Feb 14, 2007
I've changed how this works - now you can specify a localeID and also a fallbackLocale list. If the localeID is None and PyICU is available, the default locale is used. If that fails, each locale specified in fallbackLocales is tried until one works. If all that fails, then en_US is used fixed in svn trunk and will appear in 0.8.3
Status: Fixed
|
|||||||||||
| ► Sign in to add a comment | |||||||||||
