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 #1104
This is a PR drafting the release of pyo3 0.12! 🎉
I've bumped the version numbers and edited the contents of the changelog to be as consistent and simple as I could make it.
I propose the following release text (links don't work yet as they point to the 0.12 guide). Please post any suggested changes.
If I don't hear reasons otherwise, I plan to put this release live on Saturday evening. (12th September)
This release has seen a few careful revisions to the PyO3 API with the goal of making it easier to learn and use. The
PyErr
type has been reworked to implementstd::error::Error
. TheFromPy
trait is removed. ThePyObject
struct is now just a simple type alias toPy<PyAny>
.Also added is a new
#[derive(FromPyObject)]
macro, which enables a convenient way to accept arguments of the Python "type"Union
. (See the guide entry on this new feature.)There have been many other improvements and bugfixes too numerous to go into detail here. For the full list, see the CHANGELOG.
Many thanks to you all who have helped design and implement this release!