-
Notifications
You must be signed in to change notification settings - Fork 831
Add #[pyo3(default)]
option for FromPyObject
derives
#4643
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
Comments
#[pyo3(default)]
option for `FromPyObject derives#[pyo3(default)]
option for FromPyObject
derives
Implemented in #4829 |
I saw the PR merged, and some releases have happened since, but it doesn't seem available in
Is this behind a feature flag or is it planned for a later release? Or am I just holding it wrong 😖 |
This only landed after the initial 0.23 release. We usually do not backport new features, so this will be available from 0.24. We plan to release that soonish, see #4905. |
Awesome! Thank you |
Uh oh!
There was an error while loading. Please reload this page.
Continuing from #3605
The request is to add a
#[pyo3(default)]
attribute to allow missing values to be filled in, similar to serde. Note thatserde
allowsOption<T>
fields to be missing and fills them withNone
by default without requiring the attribute; in the linked discussion we agreed that was too implicit for us here.The text was updated successfully, but these errors were encountered: