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: docs/user/Interoperability.md
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -402,12 +402,9 @@ class MyPythonClass:
402
402
403
403
### Supported messages
404
404
405
-
The majority (with some exceptions) of the interop messages are supported by the interop behavior extension API, as
406
-
shown in the table below.
407
-
The naming convention for the `register_interop_behavior` keyword arguments follows the _snake_case_ naming convention,
408
-
i.e. the interop `fitsInLong` message
409
-
becomes `fits_in_long` and so on. Each message can be extended with a **pure python function** (default keyword
410
-
arguments, free vars and cell vars are not allowed) or a **boolean constant**.
405
+
The majority (with some exceptions) of the interop messages are supported by the interop behavior extension API, as shown in the table below.
406
+
The naming convention for the `register_interop_behavior` keyword arguments follows the _snake_case_ naming convention, i.e. the interop `fitsInLong` message
407
+
becomes `fits_in_long` and so on. Each message can be extended with a **pure python function** (default keyword arguments, free vars and cell vars are not allowed) or a **boolean constant**.
411
408
The table below describes the supported interop messages:
412
409
413
410
| Message | Extension argument name | Expected return type |
0 commit comments