[issue3061] time.strftime() always decodes result with UTF-8

Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue3061] time.strftime() always decodes result with UTF-8

Martin v. Löwis added the comment: Committed as r73043, r73044 -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue3061] time.strftime() always decodes result with UTF-8

Benjamin Peterson added the comment: 2009/5/29 Martin v. Löwis : > > Martin v. Löwis added the comment: > > Benjamin Peterson wrote: >> Benjamin Peterson added the comment: >> >> Can you use test_support.run_with_locale? > > I don't think so. IIUC, run_with_locale will fallback to not > settin

[issue3061] time.strftime() always decodes result with UTF-8

Martin v. Löwis added the comment: Benjamin Peterson wrote: > Benjamin Peterson added the comment: > > Can you use test_support.run_with_locale? I don't think so. IIUC, run_with_locale will fallback to not setting the locale if none of the listed locales actually works on the system. This wou

[issue3061] time.strftime() always decodes result with UTF-8

Benjamin Peterson added the comment: Can you use test_support.run_with_locale? -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue3061] time.strftime() always decodes result with UTF-8

Changes by R. David Murray : -- versions: +Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue3061] time.strftime() always decodes result with UTF-8

Martin v. Löwis added the comment: It's difficult to test. The only test I can think of is one that gets skipped if the fr_FR (say) locale is not configured. The test would then try to find out what the name of February is, which should return a string (see issue5562). -- _

[issue3061] time.strftime() always decodes result with UTF-8

Benjamin Peterson added the comment: The patch looks good. (Can this be tested?) -- nosy: +benjamin.peterson ___ Python tracker ___ __

[issue3061] time.strftime() always decodes result with UTF-8

Martin v. Löwis added the comment: Here is a patch that resolves this issue for systems supporting wcsftime, which should be the majority of systems on which the problem can occur. -- keywords: +patch priority: high -> release blocker Added file: http://bugs.python.org/file14113/wcsftim

[issue3061] time.strftime() always decodes result with UTF-8

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue3061] time.strftime() always decodes result with UTF-8

Martin v. Löwis added the comment: Is it possible to find out what specific encoding is being used? In most cases, nl_langinfo(CODESET) would be the right choice, but that depends on the LC_CTYPE category. If available, wcsftime should be used. In any case, I think issue5903 and issue5562 are

[issue3061] time.strftime() always decodes result with UTF-8

Jeroen Ruigrok van der Werven added the comment: As C99 section 7.23.3.5 states: "Each conversion specifier is replaced by appropriate characters as described in the following list. The appropriate characters are determined using the LC_TIME category of the current locale and by the values of z

[issue3061] time.strftime() always decodes result with UTF-8

New submission from Georg Brandl <[EMAIL PROTECTED]>: It decodes the system strftime's result using TZNAME_ENCODING which is also used to decode timezone names. This may be correct for timezone names themselves (I don't know), but the strftime result is encoded in the LC_TIME encoding - at least