Mention no subclassing of Python classes in docs
This commit is contained in:
parent
23fd73eb57
commit
2855b9d508
|
@ -267,6 +267,10 @@ Consult the table below to determine which type your constructor should return:
|
|||
|
||||
By default, `object`, i.e. `PyAny` is used as the base class. To override this default,
|
||||
use the `extends` parameter for `pyclass` with the full path to the base class.
|
||||
Currently, only classes defined in Rust and builtins provided by PyO3 can be inherited
|
||||
from; inheriting from other classes defined in Python is not yet supported
|
||||
([#991](https://github.com/PyO3/pyo3/issues/991)).
|
||||
|
||||
|
||||
For convenience, `(T, U)` implements `Into<PyClassInitializer<T>>` where `U` is the
|
||||
base class of `T`.
|
||||
|
@ -340,7 +344,7 @@ impl SubSubClass {
|
|||
# });
|
||||
```
|
||||
|
||||
You can also inherit native types such as `PyDict`, if they implement
|
||||
You can inherit native types such as `PyDict`, if they implement
|
||||
[`PySizedLayout`]({{#PYO3_DOCS_URL}}/pyo3/type_object/trait.PySizedLayout.html).
|
||||
This is not supported when building for the Python limited API (aka the `abi3` feature of PyO3).
|
||||
|
||||
|
|
Loading…
Reference in New Issue