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.

Author ssc
Recipients docs@python, ezio.melotti, r.david.murray, ssc
Date 2011-09-19.17:37:12
SpamBayes Score 1.45611e-08
Marked as misclassified No
Message-id <1316453833.43.0.828185550098.issue13010@psf.upfronthosting.co.za>
In-reply-to
Content
from my observations, david is correct, but this is not limited to os x. i have checked out and rebuilt python twice on a linux system (kubuntu 10.10 i386 virtual machine):

1. in a 'conventional' setup using a local (i.e. guest) harddrive formatted with a case-sensitive file system such as ext4, the built executable is called 'python' as one would expect.

2. in my setup mounting the source code folder from a cifs/samba share provided by the host, the executable is called 'python.exe': samba is not case sensitive.

once you know about case sensitivity and python / Python, the sentence in the docs makes absolute sense. before that, it looks like someone has mixed up os names.

suggestion for a rephrase: instead of

"Once CPython is done building you will then have a working build that can be run in-place; ./python on most machines (and what is used in all examples), ./python.exe on OS X (when on a case-insensitive filesystem, which is the default)."

"Once CPython is done building you will then have a working build that can be run in-place; ./python on most machines (and what is used in all examples), ./python.exe wherever a case-insensitive filesystem is used (e.g. the OS X default setting)."
History
Date User Action Args
2011-09-19 17:37:13sscsetrecipients: + ssc, ezio.melotti, r.david.murray, docs@python
2011-09-19 17:37:13sscsetmessageid: <1316453833.43.0.828185550098.issue13010@psf.upfronthosting.co.za>
2011-09-19 17:37:12ssclinkissue13010 messages
2011-09-19 17:37:12ssccreate