Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

README slight error re OSX #49676

Closed
MLModel mannequin opened this issue Mar 5, 2009 · 6 comments
Closed

README slight error re OSX #49676

MLModel mannequin opened this issue Mar 5, 2009 · 6 comments
Assignees
@birkenfeld
Labels
docs Documentation in the Doc dir

Comments

@MLModel
Copy link
Mannequin

MLModel mannequin commented Mar 5, 2009

BPO 5426
Nosy @gvanrossum, @birkenfeld, @MLModel
Files
  • unnamed
  • unnamed
    		•

    Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = 'https://github.com/birkenfeld'
closed_at = <Date 2009-03-05.17:17:54.267>
created_at = <Date 2009-03-05.16:44:28.067>
labels = ['invalid', 'docs']
title = 'README slight error re OSX'
updated_at = <Date 2009-03-05.20:21:04.124>
user = 'https://github.com/MLModel'

    bugs.python.org fields:

    activity = <Date 2009-03-05.20:21:04.124>
actor = 'MLModel'
assignee = 'georg.brandl'
closed = True
closed_date = <Date 2009-03-05.17:17:54.267>
closer = 'gvanrossum'
components = ['Documentation']
creation = <Date 2009-03-05.16:44:28.067>
creator = 'MLModel'
dependencies = []
files = ['13249', '13250']
hgrepos = []
issue_num = 5426
keywords = []
message_count = 6.0
messages = ['83203', '83204', '83205', '83208', '83209', '83216']
nosy_count = 3.0
nosy_names = ['gvanrossum', 'georg.brandl', 'MLModel']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue5426'
versions = ['Python 3.0', 'Python 3.1']
    @MLModel
    Copy link
    Mannequin Author

    MLModel mannequin commented Mar 5, 2009

    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.

    @MLModel MLModel mannequin assigned birkenfeld Mar 5, 2009
    @MLModel MLModel mannequin added the docs Documentation in the Doc dir label Mar 5, 2009
    @birkenfeld
    Copy link
    Member

    So it is just called "python"?

    @gvanrossum
    Copy link
    Member

    What makes you think it is not called python.exe? Maybe you're confused
    by the Finder's auto-hiding of externsions?

    @MLModel
    Copy link
    Mannequin Author

    MLModel mannequin commented Mar 5, 2009

    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 Python.app and IDLE.app. 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

    @gvanrossum
    Copy link
    Member

    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.

    @MLModel
    Copy link
    Mannequin Author

    MLModel mannequin commented Mar 5, 2009

    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

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Assignees

    @birkenfeld birkenfeld

    Labels
    docs Documentation in the Doc dir
    Projects
    None yet
    Milestone
    No milestone
    Development

    No branches or pull requests
    2 participants
    @birkenfeld @gvanrossum