Issue 4044: test_output_textcalendar fails on non-englisch locale (original) (raw)
Issue4044
Created on 2008-10-05 12:18 by oefe, last changed 2022-04-11 14:56 by admin. This issue is now closed.
Messages (5) | ||
---|---|---|
msg74339 - (view) | Author: Martina Oefelein (oefe) | Date: 2008-10-05 12:18 |
test_output_textcalendar (in test_calendar.py) fails if the environment variable LANG is set to a non-english locale. Python 3.0rc1 on MacOSX 10.5.5 $ LANG=de_DE.UTF-8 ./python.exe -E -bb ./Lib/test/regrtest.py -l test_calendar test_calendar test test_calendar failed -- errors occurred; run in verbose mode for details 1 test failed: test_calendar $ LANG=en_US.UTF-8 ./python.exe -E -bb ./Lib/test/regrtest.py -l test_calendar test_calendar 1 test OK. | ||
msg109565 - (view) | Author: Mark Lawrence (BreamoreBoy) * | Date: 2010-07-08 18:35 |
It would be a lot of work to fix this as the month names are hardcoded in English in test_calendar.py | ||
msg109755 - (view) | Author: R. David Murray (r.david.murray) * ![]() |
Date: 2010-07-09 15:44 |
This passes for me on linux (2.7), which is what I would expect, since the locale should not actually affect a python program unless locale.setlocale is called, which regrtest doesn't do. I also tried OSX 2.7+, and the 10.4 system python (2.6.1). test_calendar passed using the specified command line in all cases. Can anyone reproduce this issue? | ||
msg109787 - (view) | Author: R. David Murray (r.david.murray) * ![]() |
Date: 2010-07-09 19:13 |
As mentioned in #4045, I believe this is a problem with the user's local Python setup and not a Python bug. | ||
msg110019 - (view) | Author: Martina Oefelein (oefe) | Date: 2010-07-11 14:44 |
Did you test it Python *3.0*? Apparently, the issue does not happen in Python 2.x, and also not in Python 3.1.2. Apparently it was introduced somewhere in Python 3.0, and later fixed. I retested the issue in Python 3.0.1 on Mac OS X 10.6.4, using a freshly unpacked tarball, built with ./configure && make and it still happens. To avoid influences of the user environment, I repeated the test in a newly created test account. Same issue. The issue doesn't happen in Python 2.6, 2.6.5, 2.7, or 3.1.2, however. |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-11 14:56:40 | admin | set | github: 48294 |
2010-07-11 14:55:46 | r.david.murray | set | resolution: works for me -> out of date |
2010-07-11 14:44:30 | oefe | set | messages: + |
2010-07-09 19:13:56 | r.david.murray | set | status: pending -> closedmessages: + |
2010-07-09 15:44:32 | r.david.murray | set | status: open -> pendingnosy: + r.david.murraymessages: + resolution: works for mestage: resolved |
2010-07-08 18:35:18 | BreamoreBoy | set | nosy: + BreamoreBoymessages: + versions: + Python 3.1, Python 2.7, Python 3.2, - Python 3.0 |
2008-10-05 12🔞46 | oefe | create |