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

begin drafting Bound<T> migration guide #3693

Closed
wants to merge 2 commits into from

Conversation

davidhewitt
Copy link
Member

This PR is a start of the migration guide to Bound<T>. I think there's still a lot more to be added here, but I wanted to push this anyway so that we can have a central place to start collecting migration notes as well as agree on the way we want to communicate this to users.

In addition to the major API type overhaul, PyO3 has needed to make a few small breaking adjustments to other APIs to close correctness and soundness gaps.

The recommended steps to update to PyO3 0.21 is as follows:
1. Add compatibility code to convert new `Bound<T>` smart pointers back to GIL Refs
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok I think this is not the approach we are taking any more, I'll come back to rewrite this section later.

@davidhewitt
Copy link
Member Author

Superseded by #3707

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant