On 27/05/2015 20:30, Gisle Vanem wrote:
Zachary Ware wrote:
Is there any particular reason you're setting PYTHONHOME in the first
place?
I have several GNU Makefiles that picks up this variable
(to find Python.h, python*.lib etc.). But using Python 27
and 35 w/o having a %PYTHONHOME set, seem
Zachary Ware wrote:
Is there any particular reason you're setting PYTHONHOME in the first
place?
I have several GNU Makefiles that picks up this variable
(to find Python.h, python*.lib etc.). But using Python 27
and 35 w/o having a %PYTHONHOME set, seems to work fine.
I have to revise those Ma
On Wed, May 27, 2015 at 1:13 PM, Gisle Vanem 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
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 th
