On Sun, Mar 20, 2016 at 5:33 PM, wrote:
> On Wednesday, October 14, 2015 at 9:06:11 PM UTC+2, John S. James wrote:
>> I installed 3.5.0 today and it's working fine -- either from the command
>> prompt, or running a .py script.
>>
>> But the Python 3.4 that was previously
On Wednesday, October 14, 2015 at 9:06:11 PM UTC+2, John S. James wrote:
> I installed 3.5.0 today and it's working fine -- either from the command
> prompt, or running a .py script.
>
> But the Python 3.4 that was previously installed on the computer had a
> Python34 folder, which contained
eryksun wrote:
Here's a slightly simpler way to open the folder:
py -3.5 -c "import os, sys; os.startfile(sys.prefix)"
And what to do if the Pylauncher itself seems confused or the
Registry settings for PythonCore is messed up? The WOW64 mess
MS has have seems to have caused some
Thank you, this is very helpful.
John
On Wed, Oct 14, 2015 at 3:31 PM, Zachary Ware wrote:
> On Wed, Oct 14, 2015 at 2:05 PM, John S. James
> wrote:
> > I installed 3.5.0 today and it's working fine -- either from the command
> prompt, or
eryksun wrote:
The version of py.exe distributed with Python 3 is a 32-bit
application, so when the debug output says it's looking in the
"native" registry, it's referring to the WOW64 redirected registry
path, i.e. "HKLM\Software\Wow6432Node\Python". If py.exe can't find
your installation of
On 10/15/15, Gisle Vanem wrote:
>
> This is non-sense. I do have Python2 + 3 both on PATH (but both 32-bits).
> Not sure if PyLauncher looks for 64-bit registry entries only.
Running "py -3" doesn't use PATH. The launcher only uses PATH when
evaluating "/usr/bin/env" in a
On 10/15/15, Gisle Vanem wrote:
>
> Thanks for the detailed info. I fixed some paths under:
>HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\3.5-32
>
> Now my Python3.5 almost works. But something is wrong with the
> Python3 sys.prefix:
>c:> py -2 -c "import os, sys;
I installed 3.5.0 today and it's working fine -- either from the command
prompt, or running a .py script.
But the Python 3.4 that was previously installed on the computer had a Python34
folder, which contained DDLs, Doc, include, Lib, and various other folders and
files. I haven't found a
On 2015-10-14 20:05, John S. James wrote:
I installed 3.5.0 today and it's working fine -- either from the
command prompt, or running a .py script.
But the Python 3.4 that was previously installed on the computer had
a Python34 folder, which contained DDLs, Doc, include, Lib, and
various other
> Where can I find that folder? Or can I just ignore it for now (and get
the documentation elsewhere)?
If the install was done for "all users" on the machine, then the Python
installation directory will be under " %SystemRoot%\Program Files\" for
64-bit or "%SystemRoot%\Program Files (x86)\" for
On Wed, Oct 14, 2015 at 2:05 PM, John S. James wrote:
> I installed 3.5.0 today and it's working fine -- either from the command
> prompt, or running a .py script.
>
> But the Python 3.4 that was previously installed on the computer had a
> Python34 folder, which contained
On 10/14/15, Zachary Ware wrote:
>
> You can find where Python is installed using Python itself: try `py
> -3.5 -c "import sys, os;os.system('explorer ' + sys.prefix)"` at the
> Command Prompt,
Here's a slightly simpler way to open the folder:
py -3.5 -c
12 matches
Mail list logo