Skip to content

docs: link practical extension patterns and legacy C-API porting guides #2159

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.

Sign up for GitHub

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

Open
harshitethic wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: link practical extension patterns and legacy C-API porting guides #2159

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions source/guides/packaging-binary-extensions.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -228,6 +228,15 @@ The CPython :doc:`Extending and Embedding <python:extending/index>`
guide includes an introduction to writing a
:doc:`custom extension module in C <python:extending/extending>`.

For practical examples of reference-count ownership, error handling, and
creating safe extension objects, see the
`Python Extension Patterns guide <https://pythonextensionpatterns.readthedocs.io/en/latest/>`_.

If you maintain a *legacy* C extension that must run on both Python 2 and
Python 3, the `py3c porting guide <https://py3c.readthedocs.io/en/latest/>`_
documents compatibility macros and migration steps. Python 2 has reached
end-of-life; new extensions should target supported Python 3 releases.

FIXME: Elaborate that all this is one of the reasons why you probably
*don't* want to handcode your extension modules :)

Expand Down
Loading