On python, because of the Gil, multi processing should always be preferred if possible.

If you do want to try, just start a docker container and try inside there. That should negate all risk

Couldn’t get single quotes to type on my phone, but best to always use them for problems like that, to completely get rid of shell interference.

rm ./—rf\ \*

Am I missing something?

It’s easy to set the path to include the venv in the Dockerfile, that way you never have to activate, either in the run line, nor if you exec into it. Also this makes all your custom entry points super easy to use. Bonus, it’s super easy to use uv to get super fast image builds like that. See this example https://gist.github.com/dwt/6c38a3462487c0a6f71d93a4127d6c73

Did you catch that a Microsoft employee found the xz exploit?

TIL that pillow-heic is a thing. Thanks!