| msg62892 - (view) |
Author: Michael Otteneder (motteneder) |
Date: 2008-02-24 10:26 |
| Python seems to fail silently when LANG enviroment variable is set to a bad value. In Mac OS X Leopard it is set too UTF-8 for instance which does not seem to be valid. Python fails building the modules during make and the generated python.exe is unable to output anything. Setting the LANG variable to C or some other valid value fixes the problem. But I suppose python should fail more verbose in case of a bad locale,or maybe it should fallback to a standard locale. |
|
|
| msg63039 - (view) |
Author: Facundo Batista (facundobatista) *  |
Date: 2008-02-26 12:19 |
| Same here, Ubuntu on x86 32b. Doing first a "make clean", ./configure runs ok. But then, in the "make": ... File "/home/facundo/devel/reps/python/py3k/Lib/locale.py", line 479, in setlocale return _setlocale(category, locale) locale.Error: unsupported locale setting make: *** [sharedmods] Error 1 Full make output is attached. The problem seems to be in the setlocale module. I compiled everything with LANG in es_AR.UTF-8, but then executing Python again with a bad locale: facundo@virtub:~/devel/reps/python/py3k$ LANG=UTF-8 ./python Python 3.0a2+ (py3k:61084, Feb 26 2008, 10:12:19) [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import locale >>> locale.getpreferredencoding() Traceback (most recent call last): File "", line 1, in File "/home/facundo/devel/reps/python/py3k/Lib/locale.py", line 515, in getpreferredencoding setlocale(LC_CTYPE, "") File "/home/facundo/devel/reps/python/py3k/Lib/locale.py", line 479, in setlocale return _setlocale(category, locale) locale.Error: unsupported locale setting >>> Regards, |
|
|
| msg63042 - (view) |
Author: Michael Otteneder (motteneder) |
Date: 2008-02-26 14:26 |
| Interestingly it fails with a different error message on Mac. The Ubuntu one is at least helpful. I get this during make(configure also runs fine) : gcc -u _PyMac_Error -o python.exe \ Modules/python.o \ libpython3.0.a -ldl make: *** [sharedmods] Error 1 The created python.exe also behaves very strange: Tinuviel:py3k mc$ ./python.exe Python 3.0a2+ (py3k:61071, Feb 26 2008, 14:50:42) [GCC 4.0.1 (Apple Inc. build 5465)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> print("hello") >>> exit() >>> exit() >>> dfklasjd >>> Locales: Tinuviel:py3k mc$ locale LANG= LC_COLLATE="C" LC_CTYPE="UTF-8" LC_MESSAGES="C" LC_MONETARY="C" LC_NUMERIC="C" LC_TIME="C" LC_ALL= Solution: set LANG to "C" or some other valid value. |
|
|
| msg63044 - (view) |
Author: Michael Otteneder (motteneder) |
Date: 2008-02-26 14:31 |
| On my system I get different results. The error message is everything but useful. My Output: gcc -u _PyMac_Error -o python.exe \ Modules/python.o \ libpython3.0.a -ldl make: *** [sharedmods] Error 1 Tinuviel:py3k mc$ ./python.exe Python 3.0a2+ (py3k:61071, Feb 26 2008, 14:50:42) [GCC 4.0.1 (Apple Inc. build 5465)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> print("hello") >>> exit() >>> exit() >>> dfklasjd >>> Locales: LANG= LC_COLLATE="C" LC_CTYPE="UTF-8" LC_MESSAGES="C" LC_MONETARY="C" LC_NUMERIC="C" LC_TIME="C" LC_ALL= |
|
|
| msg75726 - (view) |
Author: STINNER Victor (vstinner) * |
Date: 2008-11-11 03:25 |
| Can you retry with Python 3.0rc2? |
|
|
| msg75813 - (view) |
Author: Wang Chun (wangchun) |
Date: 2008-11-13 06:12 |
| This issue remains unsolved in the latest python 3.0rc2+ subversion repository as of 2008-11-13. |
|
|
| msg77318 - (view) |
Author: Mark Dickinson (mark.dickinson) * |
Date: 2008-12-08 16:13 |
| See issue 4585, which appears to be the same problem. |
|
|
| msg77321 - (view) |
Author: Mark Dickinson (mark.dickinson) * |
Date: 2008-12-08 16:23 |
| I think I've traced the 'no output' problem back to the device_encoding function in Modules/posixmodule.c. The problem occurs when this function is called to try to get the encoding for stdout. On my machine, if I do: LC_CTYPE="UTF-8" ./python.exe then the nl_langinfo call in device_encoding returns an empty string. If I do LC_CTYPE="bogus" ./python.exe then it returns "US-ASCII" and if I do LC_CTYPE="en_US.UTF-8" ./python.exe then it returns "UTF-8". In the first case (where the encoding is set to ""), any subsequent attempts to send anything to stdout result in a LookupError with the message "unknown encoding". But of course, since this exception message is itself sent to stdout (or possibly stderr?) the same problem occurs again and we just don't see any output. I don't yet know why this causes the module build to fail, or why exit() doesn't work. I think we should try to get this fixed before 3.0.1. Any help would be welcomed. |
|
|
| msg77325 - (view) |
Author: Mark Dickinson (mark.dickinson) * |
Date: 2008-12-08 16:48 |
| Could someone please try the attached patch and see if it solves the problem. I'm not sure whether Facundo's problem is the same issue or not. |
|
|
| msg77616 - (view) |
Author: Stuart Woodward (stuartcw) |
Date: 2008-12-11 15:28 |
| I'm running on Mac OS X. I applied the patch .patch and it solved the "make: *** [sharedmods] Error 1" problem. A cursory test of /usr/local/bin/python3.0 was successful. |
|
|
| msg77623 - (view) |
Author: Mark Dickinson (mark.dickinson) * |
Date: 2008-12-11 18:09 |
| Thanks, Stuart! I've committed the fix in r67703 and r67704, so it should appear in 3.0.1. This should fix the silent build failure, and the zero-output interpreter. The behaviour is still not ideal: a bad LC_CTYPE setting causes sys.stdout and sys.stdin to have their encodings set to 'ascii'. 'UTF-8' would probably be a better guess, on OS X. But this is a lesser problem. To fix it, we should try to understand why nl_langinfo is returning an empty string in the first place. But maybe only Apple knows the answer to that one. :) |
|
|