[issue1342] Crash on Windows if Python runs from a directory with umlauts

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Fixed as r64126, using Py_FileSystemDefaultEncoding. I close this issue, and open issue3080 to rewrite all functions in import.c with full unicode in mind. -- status: open -> closed ___ Pyth

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Here is a quick fix, that decodes filenames using Py_FileSystemDefaultEncoding, to let the release pass. I am still working on a version that keep PyObjects* as long as possible, but it will be a major change. -- keywords: +pa

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: See #2798 for the non-Windows case, with a patch. __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: There are some problems under Linux too: $ pwd /home/antoine/py3k/héhé $ ./python Fatal Python error: Py_Initialize: can't initialize sys standard streams Traceback (most recent call last): File "/home/antoine/py3k/pristine/Lib/encodings/__

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Christian Heimes <[EMAIL PROTECTED]> added the comment: I'm increasing the severity of the bug. It's a still a major show stopper for non-English Windows users. For example see #2780 -- priority: normal -> release blocker __ Tracker <[EMAIL PROTECTED]>

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Changes by Giovanni Bajo: -- nosy: +rasky __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Changes by Georg Brandl: -- keywords: -rfe __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Amaury Forgeot d'Arc added the comment: Agreed. I will try to stay with PyObjects* until really needed by a system call. __ Tracker <[EMAIL PROTECTED]> __ __

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Martin v. Löwis added the comment: Please don't use the FileSystemEncoding on Windows for sys.path items. Instead, it should use the wide API to perform all system calls. Py3k shouldn't ever use the file system encoding for anything on Windows. __ Tracker <[EMAIL

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Amaury Forgeot d'Arc added the comment: Assign to myself. Among the things to do, use Py_FileSystemDefaultEncoding (=mbcs on Windows) to encode sys.path items; likewise in NullImporter_init and other functions. So many places to change, we need serious testcases. -- assignee: -> amaury.

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Christian Heimes added the comment: I'm setting the priority to normal. The issue isn't resolved but it's not critical for the next alpha release. By the way what's your ETA for the next alpha, Guido? -- priority: high -> normal __ Tracker <[EMAIL PROTECT

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Guido van Rossum added the comment: If this doesn't cause any problems on other platforms, go for it. __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-l

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Christian Heimes added the comment: I like to move _PyExc_Init() before _PySys_Init() and set sys.prefix, exec_prefix and executable with PyUnicode_DecodeFSDefault(). Without the changes Python is seg faulting on Windows when the path contains non ASCII chars. With the patch it is failing with a

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Christian Heimes added the comment: I've checked in part of the patch in r58837. It doesn't solve the problem but at least it prevents Python from seg faulting on Windows. -- keywords: +py3k, rfe priority: -> high resolution: -> accepted __ Tracker <[EM

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Christian Heimes added the comment: Hi Martin! Thomas Wouters said on #python that you have the Windows Fu to fix the problem. Parts of the Python API for file paths, sys.path and os.environ have to be reimplemented using the wide char API. -- nosy: +loewis

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Christian Heimes added the comment: The bug is related to http://bugs.python.org/issue1262 -- nosy: +gvanrossum severity: normal -> urgent __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Christian Heimes added the comment: I've added a fprintf(stderr, "%s", path) to makepathobject(). I suspect that PC/getpathp.c doesn't handle non ASCII chars correctly. It's using char instead of w_char all over the place. Could that be related to the issue, Neal? Microsoft Windows XP [Version 5

[issue1342] Crash on Windows if Python runs from a directory with umlauts

Christian Heimes added the comment: The patch fixes parts of the problem. At least Python doesn't crash any more when run from a directory with non ASCII chars. It just fails with an import error in initstdio(). Added file: http://bugs.python.org/file8633/py3k_more_win_fsencoding.patch

[issue1342] Crash on Windows if Python runs from a directory with umlauts

New submission from Christian Heimes: Python 3.0 doesn't run from a directory with umlauts and possible other non ASCII chars. I renamed my development folder from C:\dev\ to c:\test äöüß name\. Python crashes after a few moments before it can reach its shell. python30.dll!PyErr_SetObje