-
-
Notifications
You must be signed in to change notification settings - Fork 105
Python 3.11 - 3.13 Line number fixes #156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…n 3.13 object to a python 3.12 object since both of those versions do the same thing. Also added some stuff to fix some control flow issues in 3.13 as there are some cache instructions that mess up some targets
…he python 3.13 object to a python 3.12 object since both of those versions do the same thing. Also added some stuff to fix some control flow issues in 3.13 as there are some cache instructions that mess up some targets" This reverts commit eaeae09.
Co-authored-by: Joel Flores <[email protected]>
|
@rocky From my understanding, there are some tests that cover code object members like the line tables in I have mostly been testing manually and with |
Yes, when I run the tests I see
which seems clear enough what was up there.
Yes, please.
Thanks for the PR and the work. Please give me a couple of days to get to this. Things have been a bit busy recently. |
|
Looks very good. Thanks for doing this. "black" wants to reformat "bytecode.py", but I will do that after the merge. Sorry for the delay. I wanted to make sure I understood what's up here. |
|
Thanks @rocky! |
At some point line numbers for these versions were messed up, not sure exactly what happened. I have been trying to test more and across multiple versions so these issues don't arise again.
Fixes:
varnamestocellswithout resolving duplicate items that may occur in both tables.