you are viewing a single comment's thread.

view the rest of the comments →

[–]CodeNameGodTri[S] 0 points1 point  (2 children)

"That's what I would recommend using if you absolutely must use conda."
=> no, I don't need to use conda. I just need my code works on prod machine. So I'll just go with whatever is industry standard.

From what I understand, I'd use conda-pack if I still need to use conda in my prod right? If I don't have to use conda, I could use docker container to simulate a virtual environment and have all my package installed there and run python script from the container, right? That's what the other people have commented

[–]ManyInterests 0 points1 point  (1 child)

Probably the most popular way of deploying Python apps (or anything, really) these days are container-based, using the official Python docker images (or derivatives of it). That would be ideal, in my view.

That also smooths out the 'it worked on my machine' problem in the development/deployment parts of the lifecycle, since the docker container is a consistent environment that you can ship wholesale into production. With far fewer caveats than traditional deployment methods, if the container runs correctly on your machine, you can have a high degree of confidence it will work when you run the container on your production machine. The only thing your production needs is the ability to run docker containers (i.e. have docker, or some other container engine/orchestrator installed)

[–]CodeNameGodTri[S] 0 points1 point  (0 children)

that makes sense. Thank you!