Skip to content
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

Proposition to drop support for <3.11 in a new fork #525

Open
thewhitegoatcb opened this issue Oct 21, 2024 · 2 comments
Open

Proposition to drop support for <3.11 in a new fork #525

thewhitegoatcb opened this issue Oct 21, 2024 · 2 comments

Comments

@thewhitegoatcb
Copy link

With the introduction of *JUMP_BACKWARD* opcodes and new exception handling table and opcodes it becomes hard to maintain old code without breaking it or affecting the new code in unexpected ways.
Similar approach has been taken with decompile3 with similar reasoning albeit with lower 3.7 version

The proposition itself consists of:

  1. Remove any code that handles <3.11 cases, for better readability and easier maintainability
  2. Add 3.11 + support
@greenozon
Copy link
Contributor

Just imagine for a moment how much men-hours where spent and invested into this project for yeas...
I guess it makes sense to split somehow the codebase
eg - different branches or maybe even different repos?..

@thewhitegoatcb
Copy link
Author

Just imagine for a moment how much men-hours where spent and invested into this project for yeas...

I don't disqualify the previous efforts. I probably should have made it clearer in the body of the post, my suggestion is to fork this repo into a new one where the proposition would apply while maintaining this repo for bugfixes mostly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants