Installed 3.5.0 successfully on Windows 10, but where is DDLs, Doc, Lib, etc?

[John S. James]

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 comparable Python35 folder anywhere. I'd like to find the 3.5 Doc folder at least.

I looked for the installation directory using the command prompt, but at c:\Users\(my name)\ there is no AppData.

Where can I find that folder? Or can I just ignore it for now (and get the documentation elsewhere)?

[Zachary Ware]

Python 3.5 changed the default install directory on Windows to better
fit in with other Windows software and to alleviate security concerns
(C:\Python34, for example, is world-writable, whereas C:\Program
Files\Python 3.5\, which is the new default all-users install
location, can only be written to by administrators). True per-user
installs are now also possible, and install to your user directory.

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, which uses the Python Launcher for Windows to start
Python 3.5 and execute a command to start a Windows Explorer instance
in the directory containing Python.

By the way, C:\Users\(your name)\AppData does exist, but is hidden by
default. It will tab-complete, though; at Command Prompt do `dir
C:\Users\(your name)\App<tab>`.

You can also get always-up-to-date documentation from
https://docs.python.org/3.5/. There's also a download page at
https://docs.python.org/3.5/download.html if you prefer a local copy
of one of the various formats available there.

Hope this helps,
--
Zach

[paul.her...@gmail.com]

> 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 32-bit Python.

[MRAB]

The AppData folder probably _is_ there, but hidden. There's a checkbox
to show hidden items. It's on the View menu in Windows 10.

[eryksun]

On 10/14/15, Zachary Ware <zachary.w...@gmail.com> 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 "import os, sys; os.startfile(sys.prefix)"

> By the way, C:\Users\(your name)\AppData does exist, but is hidden by
> default. It will tab-complete, though; at Command Prompt do `dir
> C:\Users\(your name)\App<tab>`.

You can list all files and directories using the /a switch of cmd's
dir command, and just directories (including hidden ones) using /ad,
e.g.

dir /ad %userprofile%

[John S James]

Thank you, this is very helpful.

John

On Wed, Oct 14, 2015 at 3:31 PM, Zachary Ware <zachary.w...@gmail.com> wrote:

On Wed, Oct 14, 2015 at 2:05 PM, John S. James <john2...@gmail.com> wrote:

Python 3.5 changed the default install directory on Windows to better
fit in with other Windows software and to alleviate security concerns
(C:\Python34, for example, is world-writable, whereas C:\Program
Files\Python 3.5\, which is the new default all-users install
location, can only be written to by administrators).  True per-user
installs are now also possible, and install to your user directory.

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, which uses the Python Launcher for Windows to start
Python 3.5 and execute a command to start a Windows Explorer instance
in the directory containing Python.

By the way, C:\Users\(your name)\AppData does exist, but is hidden by
default.  It will tab-complete, though; at Command Prompt do `dir
C:\Users\(your name)\App<tab>`.

You can also get always-up-to-date documentation from
https://docs.python.org/3.5/.  There's also a download page at
https://docs.python.org/3.5/download.html if you prefer a local copy
of one of the various formats available there.

Hope this helps,
--
Zach

--

John S. James

www.AgeTreatmentNews.org -  Biomedical research to slow or reverse aging; also on Twitter at AgeTreatment

Other projects: www.affinity99.org    www.MassSponsorship.org

[Gisle Vanem]

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 problems here. With:
c:\> set PYLAUNCH_DEBUG=1 & py -3 -c "import os, sys; print(sys.prefix)"

I get:
...

locating Pythons in 64bit registry
locate_pythons_for_key: unable to open PythonCore key in HKCU
locate_pythons_for_key: unable to open PythonCore key in HKLM
locating Pythons in native registry
locate_pythons_for_key: unable to open PythonCore key in HKCU
locate_pythons_for_key: F:\ProgramFiler\Python27\python.exe is a 32bit executable
...

locate_pythons_for_key: F:\ProgramFiler-x86\Python35\python.exe: Systemet finner ikke angitt bane.
locate_pythons_for_key: F:\ProgramFiler-x86\Python35\PCBuild\win32\python.exe: Systemet finner ikke angitt bane.
locate_pythons_for_key: F:\ProgramFiler-x86\Python35\PCBuild\amd64\python.exe: Systemet finner ikke angitt bane.
found no configured value for 'python3'
search for Python version '3' found no interpreter
Requested Python version (3) not installed

("Systemet finner ikke angitt bane." == "File not found").

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.

But is there a way for py.exe to use '%USERPROFILE%\Local\py.ini' only?
I failed to find any good documentation on it's format.


--
--gv

[eryksun]

On 10/15/15, Gisle Vanem <gva...@yahoo.no> 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 virtual shebang, e.g. "#!/usr/bin/env
python".

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 Python 3 in the registry, then the installation
is broken or non-standard. Try to repair or reinstall.

If python.exe can be found on PATH, then you can use "where python",
or open all found folders using a cmd shell for loop:

for /f %f in ('where python') do @start "" "%~dpf"

> But is there a way for py.exe to use '%USERPROFILE%\Local\py.ini' only?
> I failed to find any good documentation on it's format.

The launcher looks for py.ini in "%LOCALAPPDATA%", which is
"%USERPROFILE%\AppData\Local".

The ini file allows setting defaults such as setting "python3=3.5-32"
in the [defaults] section. This is documented here:

https://docs.python.org/3/using/windows.html#customization-via-ini-files

The [commands] section is undocumented, but this section only creates
convenience commands for use with shebangs. You can always use the
absolute path to an executable in the shebang if you need to associate
a script with some other Python implementation, such as PyPy.

[Gisle Vanem]

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 Python 3 in the registry, then the installation
> is broken or non-standard. Try to repair or reinstall.

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; print(sys.prefix)"
F:\ProgramFiler\Python27

c:> py -3 -c "import os, sys; print(sys.prefix)"
F:\ProgramFiler

Where should I look for the reason for this?

--
--gv

[eryksun]

On 10/15/15, Gisle Vanem <gva...@yahoo.no> 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; print(sys.prefix)"
> F:\ProgramFiler\Python27
>
> c:> py -3 -c "import os, sys; print(sys.prefix)"
> F:\ProgramFiler
>
> Where should I look for the reason for this?

The directory for 32-bit program files is localized to "Programfiler
(x86)" in Norwegian. Is Python 3.5 installed in "F:\Programfiler
(x86)\Python 3.5"? What's the value of sys.executable?

[kosv...@gmail.com]

Python 3.5, for "all users" is in C:\Users\myName\AppData\Local\Programs\Python\Python35-32

[eryk sun]

No, "%LocalAppData%\Programs\Python\PythonXY[-32]" is for a per-user
installation, unless a buggy version of the 3.5 installer failed to
update the target directory. Per-machine installs of 3.5+ default to
either "%ProgramFiles%\PythonXY" or "%ProgramFiles(x86)%\PythonXY-32",
where X and Y are the major and minor release numbers. Note that the
initial 3.5.0 release, and only 3.5.0, uses a "Python 3.5" naming
convention.