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.

Title: README slight error re OSX
Type: Stage:
Components: Documentation Versions: Python 3.0, Python 3.1
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: georg.brandl Nosy List: MLModel, georg.brandl, gvanrossum
Priority: normal Keywords:

Created on 2009-03-05 16:44 by MLModel, last changed 2022-04-11 14:56 by admin. This issue is now closed.

File name Uploaded Description Edit
unnamed MLModel, 2009-03-05 17:57
unnamed MLModel, 2009-03-05 20:21
Messages (6)
msg83203 - (view) Author: Mitchell Model (MLModel) Date: 2009-03-05 16:44
Line 136 of the 3.0 README and line 179 of the 3.1 README state that the 
executable on OSX is called python.exe. It's not.
msg83204 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2009-03-05 16:57
So it is just called "python"?
msg83205 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2009-03-05 17:17
What makes you think it is not called python.exe? Maybe you're confused
by the Finder's auto-hiding of externsions?
msg83208 - (view) Author: Mitchell Model (MLModel) Date: 2009-03-05 17:57
Nothing on OSX is ever named .exe.

On OSX building and installing Python with "configure 
--enable-framework" installs an executable just called 'python' in 
/Library/Frameworks/Python.framework/Versions/3.1/bin (using 3.1 as 
an example). It also creates double-clickable applications whose real 
name is and  Whether to see the .app extensions 
on "packages" that are applications is a Finder preference, so most 
users won't see the .app.

If the build was configured without frameworks, then an executable 
named in the Unix style -- just python -- is installed in 
/usr/local/bin (by default) or wherever else was specified with the 
configure --prefix option.

         --- Mitchell
msg83209 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2009-03-05 18:21
That sentence however does not refer to the name of the installed Python
binary, but the binary as it is built in the source tree (or a build
directory).  And there we chose to call it "python.exe" because we
couldn't call it "python" because there is already a directory named
"Python", which (on the default case-insensitive filesystem) conflicts
with the executable name.
msg83216 - (view) Author: Mitchell Model (MLModel) Date: 2009-03-05 20:21
Whoops! It didn't say "the executable that gets built is called 
python.exe", but it is in the build section, so taking things 
literally, yes, the executable is called python.exe and I maybe 
should have taken it at its word.

There's a subtle problem in the wording since "the executable" almost 
always suggests "the program you run". It's a little weird -- though 
I see your point about why it's done that way -- to build an 
executable that gets installed as a different name. (Well, maybe 
installed with  version number as part of the name.) So even if the 
README is literally correct I do think it lays a subtle trap for the 
reader that could be avoided with a slight rewording.  Not important 
-- I'm just trying to help by pointing out documentation problems as 
I come across them. Most of them have been real.

         --- Mitchell
Date User Action Args
2022-04-11 14:56:46adminsetgithub: 49676
2009-03-05 20:21:04MLModelsetfiles: + unnamed
messages: + msg83216
2009-03-05 18:21:47gvanrossumsetmessages: + msg83209
2009-03-05 17:57:49MLModelsetfiles: + unnamed
messages: + msg83208
2009-03-05 17:17:54gvanrossumsetstatus: open -> closed
nosy: + gvanrossum
resolution: not a bug
messages: + msg83205
2009-03-05 16:57:48georg.brandlsetmessages: + msg83204
2009-03-05 16:44:28MLModelcreate