You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: guide/src/type-stub.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,7 +79,5 @@ This is useful when PyO3 is not able to derive proper type annotations by itself
79
79
- Introspection only works with Python modules declared with an inline Rust module.
80
80
Modules declared using a function are not supported.
81
81
-`FromPyObject::INPUT_TYPE` and `IntoPyObject::OUTPUT_TYPE` must be implemented for PyO3 to get the proper input/output type annotations to use.
82
-
- Because `FromPyObject::INPUT_TYPE` and `IntoPyObject::OUTPUT_TYPE` are `const` it is not possible to build yet smart generic annotations for containers like `concat!("list[", T::OUTPUT_TYPE, "]")`.
83
-
See [this tracking issue](https://github.com/rust-lang/rust/issues/76560).
84
82
- PyO3 is not able to introspect the content of `#[pymodule]` and `#[pymodule_init]` functions.
85
83
If they are present, the module is tagged as incomplete using a fake `def __getattr__(name: str) -> Incomplete: ...` function [following best practices](https://typing.python.org/en/latest/guides/writing_stubs.html#incomplete-stubs).
0 commit comments