bump the linux standalone build to use python 3.13

[williballenthin]

we're currently on 3.12, but 3.13 was released Oct 2024

[v1bh475u]

Can you please explain what is to be done?

[williballenthin]

The first artifact in the following screenshot should use Python 3.13 not 3.12. Beyond that, I'll leave it up to you to explore the repository and figure out how CI builds the image. If you have specific questions, we're happy to help.

[v1bh475u]

@williballenthin For shifting to Python3.13, we need to update the dependency of ruamel-yaml-clib to next version (0.2.9 at least). Also, When I am trying to run test_run workflow, it failing for Does it run (CAPE)? due to 7z command not found. Do you have any idea for that? I am using act for testing locally.

[franklbh]

@williballenthin I'd be excited to take on this Python 3.13 update issue. I've been working with cross-version Python dependencies recently and have some ideas for making this transition smooth:

Beyond just updating the version numberI'd like to add a version verification step to ensure the build actually uses 3.13 at runtime. We could also verify the changes using containerized approach with docker.

My system is macOS, but I'm comfortable with Linux environments. Would you be willing to assign this to me? I'm prepared to start immediately and can provide regular updates on my progress. Thanks for considering!

[franklbh]

@williballenthin Hi! I just finished updating to python 3.13. I tested locally with act and it worked. Is it possible to give me the permission to push to my remote branch?

[chf0x]

@franklbh I think there is a pull request for this - https://github.com/mandiant/capa/pull/2595