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 ronaldoussoren
Recipients docs@python, ned.deily, ronaldoussoren
Date 2021-12-06.15:00:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1638802833.35.0.414122287903.issue45998@roundup.psfhosted.org>
In-reply-to
Content
There are two ways to develop against a Python.framework on MacOS:

1. Use the regular Unix pattern with "#include "Python.h", using compiler flags to select the right headers and libraries.

2. Using the native framework pattern with "#import <Python/Python.h>" and "-framework Python"

Both works, but the latter has the disadvantage of loosing control over which version of Python is used when multiple versions are installed.  The version is selected by the "Current" link in the framework, which is overwritten to point to whatever version was last installed or updated.

IMHO we should document this pitfall in the C API documentation.
History
Date User Action Args
2021-12-06 15:00:33ronaldoussorensetrecipients: + ronaldoussoren, ned.deily, docs@python
2021-12-06 15:00:33ronaldoussorensetmessageid: <1638802833.35.0.414122287903.issue45998@roundup.psfhosted.org>
2021-12-06 15:00:33ronaldoussorenlinkissue45998 messages
2021-12-06 15:00:33ronaldoussorencreate