[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: > Victor, was this ticket kept open only for the backport to distutils2? I have no idea :) It's probably fine now. Open a new and fresh issue if it's not fixed yet, this issue has a too long history. -- resolution: -> fixed status: open -> closed ___

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: Victor, was this ticket kept open only for the backport to distutils2? If everything is fixed in Python stdlib and docs, then it could be closed, as distutils2 development has stopped. -- components: -Distutils2 nosy: +dstufft versions: -3rd party ___

[issue6011] python doesn't build if prefix contains non-ascii characters

Changes by Georg Brandl : -- status: -> open ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue6011] python doesn't build if prefix contains non-ascii characters

Changes by STINNER Victor : -- resolution: fixed -> status: closed -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue6011] python doesn't build if prefix contains non-ascii characters

Changes by Éric Araujo : -- assignee: tarek -> haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue6011] python doesn't build if prefix contains non-ascii characters

Baptiste Carvello added the comment: Indeed, I retried with 534a9e274d88 (that was the tip of 3.2 sometime yesterday) and my original problem is solved. Thank you. While I was at it, I ran "make test", and got 3 unusual skips and 1 failure. The skips are test_sax, test_xml_etree and test_xm

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: I fixed #10419 in Python 3.2 and 3.3 (I applied my copy_script-2.patch fix). It is now possible to compile and install Python 3.2 and 3.3 with a non-ASCII prefix, so this issue can be done. If you have issues when compiling Python with a non-ASCII prefix (and

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: New changeset 6ad356525381 by Victor Stinner in branch 'default': Close #10419, issue #6011: build_scripts command of distutils handles correctly http://hg.python.org/cpython/rev/6ad356525381 -- ___ Python tracker <

[issue6011] python doesn't build if prefix contains non-ascii characters

Nils Philippsen added the comment: NB: it's not the shell, but the kernel which interprets the shebang line (and subsequently calls the shell /bin/sh with it if it's missing, causing funny effects when it encounters the first import line and you happen to have ImageMagick installed). ---

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: I suggest you wait for distutils2 to be 3.x-compatible and then adapt your patch to fix the bug when used with 3.2, keeping backward compat. -- ___ Python tracker ___

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: Le samedi 25 décembre 2010 à 22:35 +, Éric Araujo a écrit : > Victor: Your patch uses os.fsencode, so porting to distutils2 won’t be > easy. In Python 3.1, you can replace name=os.fsencode(name) by name=name.encode(sys.getfilesystemencoding(), 'surrogateesc

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: Baptiste: I meant that I couldn’t reproduce the bug, not that the patch had solved it. Victor: Your patch uses os.fsencode, so porting to distutils2 won’t be easy. Tarek and I have instated this policy http://wiki.python.org/moin/Distutils/FixingBugs to make s

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: Update copy_script patch: add comments to explain why the shebang have to be decodable from UTF-8 and from the script encoding. -- Added file: http://bugs.python.org/file20165/copy_script-2.patch ___ Python tracker

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: Le vendredi 24 décembre 2010 à 14:46 +, Baptiste Carvello a écrit : > the patch solves the bug for me as well (using locale "C", the > filesystem encoding is utf-8). However, I do not understand why the > patch checks that the shebang line decodes with bot

[issue6011] python doesn't build if prefix contains non-ascii characters

Baptiste Carvello added the comment: Hello, the patch solves the bug for me as well (using locale "C", the filesystem encoding is utf-8). However, I do not understand why the patch checks that the shebang line decodes with both utf-8 and the file's encoding. The shebang line is only used by

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: I can’t reproduce the crash when building in the source dir (and tests pass except for ctypes because its configure script refuses my directory path), and I can’t build in a subdir*, so this bug looks fixed. * Error messages: gcc: Parser/tokenizer_pgen.o: No suc

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: Regarding your fix to copy_script, I will have to ask python-dev about PEP 291 in py3k (i.e., should 3.2 code really be compatible with 2.3?). -- ___ Python tracker _

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: I will try tomorrow, thanks for reminding me. That was a fresh clone. I did. -- ___ Python tracker ___

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: > My build error seems actually unrelated to encoding issues. Working > directory is ASCII-only, locale is UTF-8. > > $ ./configure --with-pydebug > [snip] > $ make > [snip] > ranlib libpython3.2dm.a > gcc -pthread -Xlinker -export-dynamic -o python Modules/

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: My build error seems actually unrelated to encoding issues. Working directory is ASCII-only, locale is UTF-8. $ ./configure --with-pydebug [snip] $ make [snip] ranlib libpython3.2dm.a gcc -pthread -Xlinker -export-dynamic -o python Modules/python.o libpython3

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: Now I get an error in copy_scripts() function of Lib/distutils/command/build_scripts.py: this function adjusts Python shebang of installed Python scripts. The problem is that the shebang contains a non-ASCII character whereas the script is written into the lo

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: > The real problem is that PREFIX is not decoded using _Py_charw2char() ... Fixed by r86345. -- ___ Python tracker ___

[issue6011] python doesn't build if prefix contains non-ascii characters

Changes by Éric Araujo : -- Removed message: http://bugs.python.org/msg120820 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: I should have worn my Stupid Hat today, because I’ve made stupid commits and emails. I hadn’t updated my checkout when I made my test. The bad news is that I still have a bug after svn up: gcc -pthread -Xlinker -export-dynamic -o python Modules/python.o lib

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: Sorry: gcc -pthread -Xlinker -export-dynamic -o python Modules/python.o libpython3.2dmu.a -lpthread -ldl -lutil -lm Fatal Python error: Py_Initialize: Unable to get the locale encoding SystemError: NULL result without error in PyObject_Call Aborted make: *

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: > Fatal Python error: Py_Initialize: Unable to get the locale encoding > SystemError: NULL result without error in PyObject_Call Gotcha! r86341 fixes PyUnicode_EncodeFS(): raise an error if _Py_char2wchar_() fails. The real problem is that PREFIX is not decod

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: I reproduced the problem with the following commands: cd py3k export LANG=C export LC_ALL=C make distclean ./configure --with-pydebug --prefix=/home/haypo/tmp/py3ké make It looks like the problem is that srcdir environment variable of Makefile.pre is ".". In

[issue6011] python doesn't build if prefix contains non-ascii characters

Baptiste Carvello added the comment: A little bit more information: the error message comes from Python/pythonrun.c, line 736, in function initfsencoding. This part of the code is protected with a preprocessor #if: #if defined(HAVE_LANGINFO_H) && defined(CODESET) so I tried replacing that w

[issue6011] python doesn't build if prefix contains non-ascii characters

Baptiste Carvello added the comment: Hello, I can reproduce the exact same error as Éric. The end of the output is a little bit more informative here: Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] Fatal Python error: Py_Initialize: Unable to get the locale e

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: Of course, first export LANG and LC_ALL to C. -- ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: I can’t reliably reproduce it, but here you go: $ pwd /home/wok/python/3.2/sep-build-dir-éric♥ $ ../configure --prefix $PWD [okay] $ make [snip gcc and ar] ranlib libpython3.2m.a gcc -pthread -Xlinker -export-dynamic -o python Modules/python.o libpython3.2m.a -

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: > Same errors. Please describe exactly how you reproduced the error (write each command). r85805 fixes another bug related to this problem. Is it a better fix than distutils_makefile_encoding.patch: use surrogateescape error handler to decode the Makefile fi

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: Same errors. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: > I’m trying to build py3k on posix in a subdir called > sep-build-dir-éric, with locale set to C. Ah yes, this particular use case doesn't work: r85800 should fix it. Please retry. -- ___ Python tracker

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: Building in the same directory works. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: I’m trying to build py3k on posix in a subdir called sep-build-dir-éric, with locale set to C. I get these errors: gcc [...] -DSVNVERSION="\"`LC_ALL=C svnversion ..`\"" -o Modules/getbuildinfo.o ../Modules/getbuildinfo.c svn: Error converting entry in directory

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: > $ LC_ALL=C ./python > Fatal Python error: Py_Initialize: Unable to get the locale encoding > SystemError: NULL result without error in PyObject_Call > Abandon What is your Python version? I fixed Python 3.2, but I don't plan to fix Python 3.1 for this proble

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: I think it is: $ pwd /tmp/éric $ LC_ALL=C ./python Fatal Python error: Py_Initialize: Unable to get the locale encoding SystemError: NULL result without error in PyObject_Call Abandon -- ___ Python tracker

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: I'm not sure that the patch is still needed on Python 3.2. -- ___ Python tracker ___ ___ Python-bugs

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: +1 for distutils_makefile_encoding.patch. The doc is not updated, because it does not exist, so that’s okay; tests for the new behavior are missing. -- ___ Python tracker __

[issue6011] python doesn't build if prefix contains non-ascii characters

Changes by Nils Philippsen : -- nosy: +nils ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue6011] python doesn't build if prefix contains non-ascii characters

Changes by Éric Araujo : -- versions: +3rd party ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: For non-ascii directory name but ascii locale (eg. C locale), we have 3 choices: a- read Makefile as a binary file b- use the PEP 383 c- refuse to compile (a) doesn't seem easy because it looks like distutils use the unicode type for all paths. (b) supposes

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: Warning: "use the PEP 383" may impact other distutils component because the path may be written into to other files, which mean that we have to use errors='surrogateescape' for these files too. -- ___ Python tracke

[issue6011] python doesn't build if prefix contains non-ascii characters

Baptiste Carvello added the comment: Eric: the bug does not exist with 2.7, as the Makefile is read as bytes. It exists with 3.1.2. By the way, when I say the bug is solved on 3.2, I only mean the narrow problem of using a non-ascii prefix that *is* decodable with the current locale. I do not

[issue6011] python doesn't build if prefix contains non-ascii characters

Éric Araujo added the comment: Victor: I would like #9841 to be solved first so that we’re sure what file(s) need to be patched (and where to add a test for parsing). Baptiste: Can you try to reproduce your bug with 2.7 and 3.1? Tarek: I can take this over if you want. -- components:

[issue6011] python doesn't build if prefix contains non-ascii characters

Baptiste Carvello added the comment: Hello, I just tried your patch on latest svn (r84707), but I found out that the problem I reported can no more be reproduced. First, '_locale' seems now to be built earlier. Also, a fallback has been introduced in 'locale.getpreferredencoding'. When '_loc

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: New patch: - add encoding option to TextFile constructor - parse_makefile() uses the heuristic from text_file.diff Note: sys.getfilesystemencoding() is always set in Python 3.2 (but it may be None in Python 2.x and Python < 3.2). -- Added file: http

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: Change _io.TextIOWrapper() heuristic to choose the encoding is a bad idea. -- ___ Python tracker ___ ___

[issue6011] python doesn't build if prefix contains non-ascii characters

STINNER Victor added the comment: This issue may be related to #9561. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue6011] python doesn't build if prefix contains non-ascii characters

Changes by Éric Araujo : -- nosy: +eric.araujo, haypo versions: +Python 2.7, Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mai

[issue6011] python doesn't build if prefix contains non-ascii characters

Tarek Ziadé added the comment: Thanks, I'll work on this during this week end hopefully -- ___ Python tracker ___ ___ Python-bugs-list

[issue6011] python doesn't build if prefix contains non-ascii characters

Baptiste Carvello added the comment: OK, here is also the patch to 'Modules/_io/textio.c', as it is in fact quite trivial. Choose which one you prefer :-) Baptiste -- Added file: http://bugs.python.org/file13984/textio.diff ___ Python tracker

[issue6011] python doesn't build if prefix contains non-ascii characters

Baptiste Carvello added the comment: And here comes the patch -- keywords: +patch Added file: http://bugs.python.org/file13975/text_file.diff ___ Python tracker ___ _

[issue6011] python doesn't build if prefix contains non-ascii characters

New submission from Baptiste Carvello : I have tried to build python (version 3.1 beta 1) on linux and install it to a non-standard prefix which contains non-ascii utf-8 characters (my locale being utf-8). The build directory's path is ascii-only. The exact configure line is given in the attached