[issue8304] strftime and Unicode characters

2014-08-29 Thread Terry J. Reedy
Terry J. Reedy added the comment: I verified Marks 3.4.1 result with Idle. It strikes me as a bug that a function that maps a unicode format string to a unicode string with interpolations added should ever encode the format to bytes, lets alone using using an encoding that fails or loses

[issue8304] strftime and Unicode characters

2014-07-10 Thread Mark Lawrence
Mark Lawrence added the comment: Using 3.4.1 and 3.5.0 I get:- time.strftime(%d\u200F%A, time.gmtime()) Traceback (most recent call last): File stdin, line 1, in module UnicodeEncodeError: 'locale' codec can't encode character '\u200f' in position 2: Illegal byte sequence -- nosy:

[issue8304] strftime and Unicode characters

2012-04-25 Thread STINNER Victor
STINNER Victor victor.stin...@gmail.com added the comment: Actually the bug seems related to Windows. See also the issue #10653: wcsftime() doesn't format correctly time zones, so Python 3 uses strftime() instead. -- nosy: +haypo ___ Python

[issue8304] strftime and Unicode characters

2012-04-25 Thread Brian Curtin
Changes by Brian Curtin br...@python.org: -- nosy: -brian.curtin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8304 ___ ___ Python-bugs-list

[issue8304] strftime and Unicode characters

2010-04-04 Thread AndiDog
AndiDog andi...@web.de added the comment: Just installed Python 3.1.2, same problem. I'm using Windows XP SP2 with two Python installations (2.6.4 and now 3.1.2). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8304

[issue8304] strftime and Unicode characters

2010-04-04 Thread AndiDog
AndiDog andi...@web.de added the comment: Definitely a Windows problem. I did this on Visual Studio 2008: wchar_t out[1000]; time_t currentTime; time(currentTime); tm *timeStruct = gmtime(currentTime); size_t ret = wcsftime(out, 1000, L%d%A, timeStruct); wprintf(Lret =

[issue8304] strftime and Unicode characters

2010-04-04 Thread Brian Curtin
Changes by Brian Curtin cur...@acm.org: -- versions: -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8304 ___ ___ Python-bugs-list

[issue8304] strftime and Unicode characters

2010-04-03 Thread AndiDog
New submission from AndiDog andi...@web.de: There is inconsistent behavior in time.strftime, comparing Python 2.6 and 3.1. In 3.1, non-ASCII Unicode characters seem to get dropped whereas in 2.6 you can keep them using the necessary Unicode-to-UTF8 workaround. This should be fixed if it isn't

[issue8304] strftime and Unicode characters

2010-04-03 Thread Eric Smith
Changes by Eric Smith e...@trueblade.com: -- nosy: +eric.smith ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8304 ___ ___ Python-bugs-list mailing

[issue8304] strftime and Unicode characters

2010-04-03 Thread Ezio Melotti
Ezio Melotti ezio.melo...@gmail.com added the comment: This seems to be fixed now, on both 3.1 and 3.2. Can you try with 3.1.2 and see if it works? What operating system are you using? -- nosy: +ezio.melotti priority: - normal status: open - pending versions: -Python 2.6

[issue8304] strftime and Unicode characters

2010-04-03 Thread Ezio Melotti
Ezio Melotti ezio.melo...@gmail.com added the comment: Actually the bug seems related to Windows. -- components: +Windows nosy: +brian.curtin status: pending - open versions: +Python 3.2 ___ Python tracker rep...@bugs.python.org