This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Usual Installation Directory
Type: enhancement Stage: resolved
Components: Documentation Versions: Python 3.6, Python 3.5
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, eryksun, firatozgul, lac, steve.dower, zach.ware
Priority: normal Keywords: patch

Created on 2015-11-27 09:24 by firatozgul, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
issue25741.diff zach.ware, 2015-11-27 17:25 review
Messages (10)
msg255455 - (view) Author: Firat Ozgul (firatozgul) Date: 2015-11-27 09:24
Official documentation reads: "On Windows machines, the Python installation is usually placed in C:\Python35"

However, as of Python 3.5.0, usual installation directory on Windows is %LOCALAPPDATA%\Programs\Python.
msg255456 - (view) Author: Laura Creighton (lac) Date: 2015-11-27 10:02
Where does it go if the user hasn't set %LOCALAPPDATA% ?
msg255457 - (view) Author: Firat Ozgul (firatozgul) Date: 2015-11-27 10:20
Correct me if I am wrong, but as far as I know, %LOCALAPPDATA% is always set in Windows. When you want to install Python for just one user (which is the default), files are installed into this directory (LOCALAPPDATA). If you choose to install Python for all users, however, files are installed into %PROGRAMFILES% or %PROGRAMFILES(x86)%
msg255458 - (view) Author: Laura Creighton (lac) Date: 2015-11-27 10:28
I don't know the answer, but from the point of view of a webmaster who
gets support requests and doesn't have a windows system, it would be
very useful to already know where a person's python is supposed to
be, and thus good if the documentation said something along the
lines of:

If the user does not specify %LOCALAPPDATA% then it defaults to
<wherever that is> 

assuming there is such a default, of course.
msg255459 - (view) Author: Firat Ozgul (firatozgul) Date: 2015-11-27 10:56
Actually, under 'Using Python on Windows' at https://docs.python.org/3/using/windows.html, the documentation correctly refers to %LOCALAPPDATA% and %PROGRAMFILES% or %PROGRAMFILES(x86)% environment variables as the default installation directories for just-for-me installs and for all-user installs, respectively. The information provided in the tutorial part of the documentation (where it refers C:\Python35 as the default location) contradicts the one provided under 'Using Python on Windows'.
msg255466 - (view) Author: Zachary Ware (zach.ware) * (Python committer) Date: 2015-11-27 17:25
Here's a patch to try to modernize the whole section a bit, and to remove one of the two other instances of 'Python35' in the docs (the other instance is in the docs for pyvenv, which needs its own overhaul in a separate issue).
msg255526 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2015-11-28 04:36
That patch looks good to me.

LOCALAPPDATA is set by the operating system, typically to C:\Users\<username>\AppData\Local (at least since Vista I think? Certainly since Win7). While it's possible to customize it, people who know how to do that won't be emailing webmasters expecting technical support.
msg255532 - (view) Author: Firat Ozgul (firatozgul) Date: 2015-11-28 09:11
Maybe that part of the tutorial should also include a link to https://docs.python.org/3/using/windows.html. This document contains all the details for using Python on Windows.
msg255535 - (view) Author: Eryk Sun (eryksun) * (Python triager) Date: 2015-11-28 10:38
> LOCALAPPDATA is set by the operating system, typically to 
> C:\Users\<username>\AppData\Local (at least since Vista I
> think? Certainly since Win7

Vista introduced LOCALAPPDATA, so there's no problem referencing it in the docs for 3.5+. 

On a related note, section 3.4.4.1 [1] could be changed to use %LOCALAPPDATA% instead of referring to the shell function SHGetFolderPath and CSIDL_LOCAL_APPDATA. 

[1]: https://docs.python.org/3.5/using/windows.html#customization-via-ini-files
msg388543 - (view) Author: Eryk Sun (eryksun) * (Python triager) Date: 2021-03-12 18:00
I'm closing this issue as out of date. The tutorial now refers to the py command and also the python3.9 command from the app distribution. The patch's addition of "followed by Enter" after "Control-Z" is still needed, but it's not related to this issue.
History
Date User Action Args
2022-04-11 14:58:24adminsetgithub: 69927
2021-03-12 18:00:18eryksunsetstatus: open -> closed
resolution: out of date
messages: + msg388543

stage: resolved
2015-11-28 10:38:45eryksunsetnosy: + eryksun
messages: + msg255535
2015-11-28 09:11:39firatozgulsetmessages: + msg255532
2015-11-28 04:36:35steve.dowersetmessages: + msg255526
2015-11-27 17:25:42zach.waresetfiles: + issue25741.diff
versions: + Python 3.6
nosy: + zach.ware

messages: + msg255466

keywords: + patch
2015-11-27 16:35:23brett.cannonsetnosy: + steve.dower
2015-11-27 10:56:07firatozgulsetmessages: + msg255459
2015-11-27 10:28:48lacsetmessages: + msg255458
2015-11-27 10:20:48firatozgulsetmessages: + msg255457
2015-11-27 10:02:20lacsetnosy: + lac
messages: + msg255456
2015-11-27 09:24:04firatozgulcreate