Not python, but I have had hiccups with both Go and Java when targetting x86 linux docker images. The Go stuff would make qemu choke when building multiple go binaries in parallel, and the java testcontainers I use had some sort of an issue.
In general though, I love my M1 air, but I am sticking to my workstation (5950x, 64GB, debian) for dev work for now.
Being able to control the base platform is sometimes important - in this case the target is aws lambda, and even building on Ubuntu 20.10 we ended up with links to incompatible GlibC library versions compared to the lambda runtime environment.
Quick fix for all of this - whatever platform you run the build on, do it in docker on the exact same base image that lambda uses at runtime.
I know, you’re going to tell me there’s an easy way around this with cross-compilation. But when you already have docker available , quite often everything looks like a nail.
In general though, I love my M1 air, but I am sticking to my workstation (5950x, 64GB, debian) for dev work for now.