So you're thinking of putting all your shared code into a Dockerfile, e.g. COPY...
So you're thinking of putting all your shared #python code into a Dockerfile, e.g.
COPY utils.py /shared_stuff
1) That code is not in a venv.
2) That is not a versioned package
3) docker build will break your code as be base image evolves
4) can't run unit test or execute your code
5) have to add utils.py to your code repo & .gitignore it
Self-replies
Any option that involves wheel files is correct.
But if you really want to shoot your self in the foot:
1) store utils.py in wikipedia. You really will never know what is there
2) store it in a cookie that you have use browser automation to access. It will be astonishing to maintenance devs
3) store it in bash history, it is the source control for bash, it can be source control for #python
4) store it in a random number generator, at one offset or another, there will be the bytes of utils.py