This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients amaury.forgeotdarc, belopolsky, eric.smith, gvanrossum, loewis, schmir, vstinner
Date 2011-01-06.20:52:11
SpamBayes Score 2.3250097e-06
Marked as misclassified No
Message-id <>
In-reply-to <>
On Thu, Jan 6, 2011 at 11:56 AM, Eric Smith <> wrote:
> If we're going to take this on (re-writing strftime), I think the way to do it is to have it take the locale info as a parameter, and if that parameter is NULL then look up the info in the current locale. It looks like it's still a problem to find all of the info in the locale on all platforms, though. Finding the locale info is no doubt the tricky part, as someone said.

Hm, shouldn't the libc locale support offer the same set of locales
and locale info that the libc strftime uses, on any platform? Or are
there platforms whose libc strftime has better locale support than the
libc getlocale implementation???
Date User Action Args
2011-01-06 20:52:13gvanrossumsetrecipients: + gvanrossum, loewis, amaury.forgeotdarc, belopolsky, vstinner, eric.smith, schmir
2011-01-06 20:52:11gvanrossumlinkissue3173 messages
2011-01-06 20:52:11gvanrossumcreate