Repository navigation
docs: link practical extension patterns and legacy C-API porting guides - #2159
Open
harshitethic wants to merge 1 commit into
Open
harshitethic wants to merge 1 commit into
harshitethic wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #325.\n\nThe binary extension implementation guide now points to Python Extension Patterns for practical C extension implementation and the py3c porting guide for legacy code that must span Python 2 and 3. The latter is explicitly marked as legacy rather than implying Python 2 is a recommended target.\n\nValidation: git diff --check, verified both documentation sites are currently published. Documentation-only change.
📚 Documentation preview 📚: https://python-packaging-user-guide--2159.org.readthedocs.build/en/2159/