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

Bump Python Version for faster ARM-based docker build times #543

Open
Jepson2k opened this issue Dec 19, 2024 · 2 comments
Open

Bump Python Version for faster ARM-based docker build times #543

Jepson2k opened this issue Dec 19, 2024 · 2 comments
Assignees
Milestone

Comments

@Jepson2k
Copy link
Collaborator

What is the use case for the feature?
Current arm-based docker build times are slow due to the docker build system building the wheel for the python packages z3-solver and capstone. These packages are dependencies of angr and by bumping the angr version it'll use the later version of these python packages that have pre-built binaries for ARM devices. In order to upgrade angr we need to upgrade Python.

Does the feature contain any proprietary information about another company's intellectual property?
No

How would you implement this feature?
Bumping Python, angr, and any other dependent packages.

Are there any (reasonable) alternative approaches?
No

Are you interested in implementing it yourself?
Yes

@whyitfor
Copy link
Contributor

What version of Python are you proposing updating to?

@Jepson2k
Copy link
Collaborator Author

Current thought process:

  • The newer version of angr (which uses newer versions of other packages that come with pre-build binaries for arm) requires 3.10+
  • 3.11 is standard in debian bookworm and provides significant python execution speed up.
  • Binwalk doesn't directly support python 3.12.8.

After initial testing it appears that upgrading to python 3.11 requires minimal changes to maintain 100% testing coverage.

@rbs-jacob rbs-jacob linked a pull request Jan 6, 2025 that will close this issue
1 task
@rbs-jacob rbs-jacob added this to the 3.3.0 Release milestone Jan 6, 2025
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

Successfully merging a pull request may close this issue.

3 participants