allow #[pymodule(...)]
to accept all relevant #[pyo3(...)]
options
#4330
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.
Loosely a follow-up to #4308, cc @alex
This change makes
#[pymodule]
consistent with#[pyfunction]
and#[pyclass]
in that it now accepts all the module-related#[pyo3(...)]
options directly in#[pymodule(...)]
e.g.
#[pymodule] #[pyo3(name = "foo")]
can now be the shorthand#[pymodule(name = "foo")]
.While doing this I made a few adjustments to the
#[pymodule]
macro implementation to make it more consistent with how the others are implemented. I also updated the docs on#[pymodule]
at the same time.