Re: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows

2012-10-31 Thread anatoly techtonik
On Tue, Oct 23, 2012 at 2:39 AM, Stephen J. Turnbull < turnb...@sk.tsukuba.ac.jp> wrote: > > So it shuts down abnormally. That's what an abort means, in > programming as in rocket launches. Users should be scared if this > happens; somebody really screwed up. (Unless it's themselves, and > then

Re: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows

2012-10-22 Thread Greg Ewing
Stephen J. Turnbull wrote: For most users, it doesn't matter whether an environment variable is set incorrectly without their knowledge, or if the kernel is buggy, or if the disk is corrupt. And from Python's point of view, the world as a whole no longer makes. So it shuts down abnormally. Tha

Re: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows

2012-10-22 Thread Stephen J. Turnbull
anatoly techtonik writes: > I am not a C coder and don't have any core Unix programming > background. If Python is unable to start because it can not find its > libraries, I prefer an explanative error message with standard system > error code. Even if it is Fatal Python error - this case is s

Re: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows

2012-10-22 Thread anatoly techtonik
On Mon, Oct 22, 2012 at 7:37 PM, Christian Heimes wrote: > Am 22.10.2012 18:26, schrieb anatoly techtonik: >> I don't know what is abort() on Linux, but I believe coredumps is not >> something you want to get while setting some environment variable. On >> Windows it outputs a standard crash dialog

Re: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows

2012-10-22 Thread Christian Heimes
Am 22.10.2012 18:26, schrieb anatoly techtonik: > I don't know what is abort() on Linux, but I believe coredumps is not > something you want to get while setting some environment variable. On > Windows it outputs a standard crash dialog box, which immediately > raises questions about Python stabili

Re: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows

2012-10-22 Thread anatoly techtonik
On Mon, Oct 22, 2012 at 4:40 PM, Victor Stinner wrote: >> >>> set PYTHONHOME=C:\ >>> python > > The issue #8766 is about PYTHONPATH environment variable, not > PYTHONHOME. Test on Linux with Python 3.4: > > $ PYTHONHOME=/x ./python > Fatal Python error: Py_Initialize: Unable to get the locale enco

Re: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows

2012-10-22 Thread Christian Heimes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am 22.10.2012 16:43, schrieb Barry Warsaw: > On Oct 22, 2012, at 04:30 PM, Christian Heimes wrote: > >> I think it's a bug in lsb_release, too. It should use the -E >> option in its shebang: > > Indeed, thanks! I'd forgotten about -E. > > (bug up

Re: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows

2012-10-22 Thread Barry Warsaw
On Oct 22, 2012, at 04:30 PM, Christian Heimes wrote: >I think it's a bug in lsb_release, too. It should use the -E option in >its shebang: Indeed, thanks! I'd forgotten about -E. (bug updated btw) -Barry signature.asc Description: PGP signature __

Re: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows

2012-10-22 Thread Christian Heimes
Am 22.10.2012 16:18, schrieb Barry Warsaw: > This is caused by the VMware player installer playing games with $PYTHONHOME > to try to point it at its own *Python 2* runtime, and trying to call > lsb_release (a Python 3 script on Ubuntu 12.10) while $PYTHONHOME is pointing > at the wrong runtime. >

Re: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows

2012-10-22 Thread Barry Warsaw
On Oct 22, 2012, at 03:40 PM, Victor Stinner wrote: >The issue #8766 is about PYTHONPATH environment variable, not >PYTHONHOME. Test on Linux with Python 3.4: > >$ PYTHONHOME=/x ./python >Fatal Python error: Py_Initialize: Unable to get the locale encoding >ImportError: No module named 'encodings'

Re: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows

2012-10-22 Thread Oleg Broytman
On Mon, Oct 22, 2012 at 04:31:34PM +0300, anatoly techtonik wrote: > Could anybody reopen http://bugs.python.org/issue8766 ? I can't. Even if you add a comment? > BTW, what is the role of PYTHONPATH on Windows? The same as on Unix -- it's inserted into (but not replaced) sys.path. And no

Re: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows

2012-10-22 Thread Victor Stinner
2012/10/22 anatoly techtonik : > Could anybody reopen http://bugs.python.org/issue8766 ? I can't. > Reproducible 100% with Python 3.2 and 3.3 (3.1 didn't test). > >> set PYTHONHOME=C:\ >> python The issue #8766 is about PYTHONPATH environment variable, not PYTHONHOME. Test on Linux with Python 3.4

Re: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows

2012-10-22 Thread R. David Murray
You are more likely to get action on bugs by posting to the bug tracker. That said, since 8766 was fixed, your issue is most likely a new one. Please open a new bug report. --David On Mon, 22 Oct 2012 16:31:34 +0300, anatoly techtonik wrote: > Could anybody reopen http://bugs.python.org/issue8

Re: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows

2012-10-22 Thread Christian Heimes
Am 22.10.2012 15:31, schrieb anatoly techtonik: > Could anybody reopen http://bugs.python.org/issue8766 ? I can't. > Reproducible 100% with Python 3.2 and 3.3 (3.1 didn't test). > >> set PYTHONHOME=C:\ >> python The segfault isn't caused by faulty code but by a call to abort() in Py_FatalError().

[Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows

2012-10-22 Thread anatoly techtonik
Could anybody reopen http://bugs.python.org/issue8766 ? I can't. Reproducible 100% with Python 3.2 and 3.3 (3.1 didn't test). > set PYTHONHOME=C:\ > python BTW, what is the role of PYTHONPATH on Windows? Is it a path for %INSTALLDIR%\Lib\site-packages? -- anatoly t. __