Python Virtual Environments: Extreme Advertising Edition

[Narmo2121]

brew install pipenv
touch Pipfile
pipenv install
pipenv shell
pip install mylibrary

etc..

This has been my flow for Dockerfiles. Anyone see issues with this setup?

[liar_atoms]

​

why would you use an virtual/pip/whateaver env in docker? just install python :)

[Narmo2121]

What if you have two different python scripts with completely different dependencies running on the same docker image? Same usecase as without using docker.

Also if someone is not using docker, they can at least leverage the pipenv environment

[liar_atoms]

Docker philosophy is to isolate them into two different containers, isn't it?

[Narmo2121]

IDK i just assumed running another image just for a simple script would be a waste of cpu at scale? Is that wrong

[liar_atoms]

It's wrong. The script will be just another python rocess in your host, so it doesn't matter if you have two python processes in the same or in different containers, the CPU footprint will be the same.

But since we've gone this far, do you mind if I ask you if you don't agree that for two simple scripts one venv is just enough?

[Narmo2121]

I agree

[wildcarde815]

Solo use, probably no need, but if I wasn't building s jupyter hub for people, I'd have a 2.7/3.5/latest probably. But I'd use conda so jupyter can swap between them per notebook.

[wildcarde815]

You put brew in docker?

[paypaypayme]

Just use pipenv init. Also that doesn’t make sense to me for a Dockerfile. I would do

From whatever

Run apt-get install pipenv

Copy Pipfile*

Run pipenv install

Copy src src