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: .agents/tasks/2025/08/21-0939-codetype-interface
+17Lines changed: 17 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -17,3 +17,20 @@ Here's relevant information:
17
17
* design-docs/design-001.md - shows how we write design documentation
18
18
* https://docs.python.org/3/library/sys.monitoring.html - Documentation of the Python sys.montoring API
19
19
* https://docs.python.org/3/reference/datamodel.html#code-objects - Description of Python Code Objects.
20
+
21
+
--- FOLLOW UP TASK ---
22
+
Please address any inline comments on the diff, as well as any additional instructions below.
23
+
24
+
According to the PyO3 documentation it is preferred to use instead of Py<T>. Is it possible that the code object wrapper takes that into account? Here is relevant info:
25
+
* https://pyo3.rs/v0.25.1/types.html
26
+
* https://docs.rs/pyo3/0.25.1/pyo3/index.html
27
+
28
+
Also please add usage examples to the design documentation
29
+
--- FOLLOW UP TASK ---
30
+
Please address any inline comments on the diff, as well as any additional instructions below.
31
+
32
+
According to the PyO3 documentation it is preferred to use `Bound<'_, T>` instead of Py<T>. Is it possible that the code object wrapper takes that into account? Here is relevant info:
33
+
* https://pyo3.rs/v0.25.1/types.html
34
+
* https://docs.rs/pyo3/0.25.1/pyo3/index.html
35
+
36
+
Also please add usage examples to the design documentation
0 commit comments