luxolus
/
pyo3
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #3631 from wyfo/doc_typo 

docs: fix typos
This commit is contained in:
messense 2023-12-07 12:29:00 +00:00 committed by GitHub
parent 07726aefc4 e73c795967
commit 601d9573c8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
guide/src/SUMMARY.md
View File

@ -15,8 +15,8 @@
- [Emulating numeric types](class/numeric.md)
- [Emulating callable objects](class/call.md)
- [Type conversions](conversions.md)
- [Mapping of Rust types to Python types](conversions/tables.md)]
- [Conversion traits](conversions/traits.md)]
- [Mapping of Rust types to Python types](conversions/tables.md)
- [Conversion traits](conversions/traits.md)
- [Python exceptions](exception.md)
- [Calling Python from Rust](python_from_rust.md)
- [Using `async` and `await`](async-await.md)

2
guide/src/async-await.md
View File

@ -30,7 +30,7 @@ Resulting future of an `async fn` decorated by `#[pyfunction]` must be `Send + '
As a consequence, `async fn` parameters and return types must also be `Send + 'static`, so it is not possible to have a signature like `async fn does_not_compile(arg: &PyAny, py: Python<'_>) -> &PyAny`.
However, there is an exception for method receiver, so async methods can accept `&self`/`&mut self`
However, there is an exception for method receiver, so async methods can accept `&self`/`&mut self`.
## Implicit GIL holding