Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: #513
Open points:
posonlyargs
), the fields added in py311 play a more important role and I haven't tested yet if a function teleported from e.g 3.8 to 3.11 will behave correctly despiteco_exceptiontable
not initialized properly.co_qualname
can useco_name
if missing (e.g 3.8 -> 3.11 teleportation)test_teleportation.py::test_compat
is broken, it works on the assumption thatCodeType
was broken only on 3.8, and requires a redesign to work properly on 3.11 era, I think (it currently tests 4 permutations and it will have to test 9 with 3.11)Otherwise - all local, same-version tests are passing, so this can be safely used 3.11 <-> 3.11 I think, and also teleportations of 3.11 -> lower can be used (but not the other way around until the points I mentioned are investigated).