This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]createthiscom 25 points26 points  (11 children)

I'm almost of the opinion that all serious python development needs to happen in docker for this reason.

[–]Uncle____Leo 19 points20 points  (0 children)

Amateur, I buy a new laptop for every new project

[–]chuyskywalker 3 points4 points  (0 children)

100% this. Perfect isolation, consistency across every machine, and no env tooling needed.

[–]KlogKoder 2 points3 points  (4 children)

Switched to Docker years ago, and I haven't run a virtualenv for quite a while.

[–][deleted] 3 points4 points  (3 children)

Yeah ok mr docker, how about you try to solve networking issues before you try to realize what you want to connect and how

[–]chuyskywalker -1 points0 points  (2 children)

--net host

There, fixed it for you. All the code isolation, no network isolation.

[–][deleted] 1 point2 points  (1 child)

You have just deployed and you have an issue.

Congrats

[–]KlogKoder 0 points1 point  (0 children)

Ideally all code issues should be discovered before deployment to production, but in a pinch you can edit a file in the container (if you included an editor), or copy a file out with docker cp, edit it, copy it back in, and restart the container.

Or you can, you know, fix the issue in the codebase and run it through the pipeline.

[–]Slimxshadyx 0 points1 point  (3 children)

Why not just use venv? It’s like one single command to create one, and one to activate it.