feat!: upgrade dockerfile to python 3.10 [APE-1112]

[sabotagebeats]

What I did

upgrade dockerfile to python 3.10 by using python 3.10 slim base image

How I did it

wanted to have python 3.10 as base image so that using python 3.10

How to verify it

docker build -t ape .
docker run -it --entrypoint /bin/bash ape

harambe@09814ecfcd49:~/project$ python --version
Python 3.10.12

Checklist

• All changes are completed
• New test cases have been added
• Documentation has been updated

[antazoey]

Is this a breaking change for the image? Wondering if this should happen in 0.7 versus now.

Note, you can set PYTHON_ARG="3.10" in silverback if you need to

[sabotagebeats]

this can wait for a later version if this is a breaking change, but it doesn't seem to break anything for me?

Is this a breaking change for the image? Wondering if this should happen in 0.7 versus now.

Note, you can set PYTHON_ARG="3.10" in silverback if you need to

[fubuloubu]

Is this a breaking change for the image? Wondering if this should happen in 0.7 versus now.

Note, you can set PYTHON_ARG="3.10" in silverback if you need to

I agree with @antazoey, this could be a breaking change, and there's a workaround for now

[sabotagebeats]

@antazoey should I close this or leave it open?

[fubuloubu]

I think we should migrate everything that only used 3.8 to 3.10 when we migrate things for the v0.7.0 release (such as linting CI, base image, etc.)

[github-actions]

This pull request is considered stale because it has been open 30 days with no activity. Remove stale label, add a comment, or make a new commit, otherwise this PR will be closed in 5 days.

[sabotagebeats]

I think this is now a blocker for chaosnet ApePay integration.

I tried using ARG PYTHON_VERSION="3.10" in silverback, but it does not work to accomplish the task.

#1495 (comment)

[fubuloubu]

Noting that this is breaking change for some, but hopefully impact is small