Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #91320 > unrolled thread

Re: Python 3.5 crashes on wrong %PYTHONHOME

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Python 3.5 crashes on wrong %PYTHONHOME Zachary Ware <zachary.ware+pylist@gmail.com> - 2015-05-27 14:03 -0500

#91320 — Re: Python 3.5 crashes on wrong %PYTHONHOME

On Wed, May 27, 2015 at 1:13 PM, Gisle Vanem <gvanem@yahoo.no> wrote:
> I just installed the 32-bit Python 3.5b4 via the Web-installer.
> First, I was a bit annoyed by the fact it installed under
>   'f:\ProgramFiler-x86\Python35' instead of
>   'f:\ProgramFiler\Python35' as I customided for. But I guess
> this is a WOW64 thing. I'm on Win-8.1 (64-bit).
>
> But then I noticed the whole thing crashes when calling
> python35!Py_FatalError. On a simple 'python -v' command.
>
> Presumably because my env-var:
>  PYTHONHOME=f:\Programfiler\Python27
>
> (and not 'PYTHONHOME=f:\Programfiler\Python35').
>
> Reading the message on this list, gave me the impression
> Python 2.7 and Python 3.5 can co-exist with no problem.
> Doesn't look the case so far. Is there another 'PYTHONxx'
> env-var to override 'PYTHONHOME' in this case? Or what should
> I do to keep on using both 27 and 35?

Is there any particular reason you're setting PYTHONHOME in the first
place?  It shouldn't be necessary unless you're doing something
abnormal.  I'd try unsetting it entirely and see if things just work.

-- 
Zach

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web