> Also, this way I have a set of python packages already installed.
Isn't this what virtualenv was created to get away from?
If several of your projects rely on one of the "base" packages, upgrading it (which you might want for one project) could break the other projects.
Also, having implicit dependencies on packages might lead to problems with deployment (or for other developers) because they don't know that this package is required (and you might not have realized either, since it's always available on your machine).
(I might have misunderstood your solution, though. I've never used Docker.)
Hi, nop, the reasoning behind having a base set of packages installed is that I more often than not use those.
But as I start docker off a particular folder, I could decide not to use that base folder, and then having no package pre installed, or a complete different set.
This other comment [1] clarifies my whole set up, and sheds a lot more light on how it works
Isn't this what virtualenv was created to get away from?
If several of your projects rely on one of the "base" packages, upgrading it (which you might want for one project) could break the other projects.
Also, having implicit dependencies on packages might lead to problems with deployment (or for other developers) because they don't know that this package is required (and you might not have realized either, since it's always available on your machine).
(I might have misunderstood your solution, though. I've never used Docker.)