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 loewis
Recipients kevinwatters, loewis, ocean-city
Date 2009-02-14.07:42:18
SpamBayes Score 1.5809084e-09
Marked as misclassified No
Message-id <499675D9.1080703@v.loewis.de>
In-reply-to <1234585774.11.0.722010212207.issue5249@psf.upfronthosting.co.za>
Content
> On VC6, wcsftime simply converts *format* to mbcs string, calls
> strftime, and converts result to unicode, so there is no difference
> between my patch and wcsftime.

Right.

> (Newer VC's wcsftime might have different
> implementation though) Maybe you are concerning about the cost of extra
> unicode object creation on non-windows platform? 

No. I'm concerned primarily about code cleanliness, by relying on
library code rather than implementing stuff ourselves.

OTOH, the conversion to narrow strings still needs to happen on Unix
(and probably needs to use the locale's encoding, not UTF-8), so
a uniform treatment also has a value.
History
Date User Action Args
2009-02-14 07:42:21loewissetrecipients: + loewis, ocean-city, kevinwatters
2009-02-14 07:42:20loewislinkissue5249 messages
2009-02-14 07:42:18loewiscreate