You don't really need a virtualenv
frostming.com
You don't really need a virtualenv
1–10 of 148 posts
Re: You don't really need a virtualenv
#2> One day a minor release of Python is out
It is decidedly not true that I want to update my venv for every minor version bump!
I deploy to a cloud service w/ a specific version; my package manager is slow to update; I develop collaboratively using a shared container w/ a fixed version.
Updating shared resources with every new release is not always realistic, and that makes it so that I do need (or at least want) to use a virtualenv.
Re: You don't really need a virtualenv
#3Sure you can make your own package directory and develop a new package manager to point into it. But what's the point when Poetry already exists?
Re: You don't really need a virtualenv
#4This was a good article and looks like an interesting project.
Regardless of whether or not you choose to _deploy_ with Docker, _developing_ in Docker containers using the VS Code Remote extensions really solved all of Python's (and Javascript's) annoying packaging problems for me, with the bonus that you also get to specify any additional (non-Python) dependencies right there in the repo Dockerfile and have the development environment reproducible across machines and between developers. YMMV, of course, but I find this setup an order of magnitude less finicky than the alternatives and can't imagine going back.
Re: You don't really need a virtualenv
#5Sure you can make your own package directory and develop a new package manager to point into it. But what's the point when Poetry already exists?
As the authors said - no more virtual envs.
Re: You don't really need a virtualenv
#6As a Ruby and Python developer I often wonder why Ruby doesn't need a virtual env. What did Ruby get right that Python didn't?
Re: You don't really need a virtualenv
#7Sure you can make your own package directory and develop a new package manager to point into it. But what's the point when Poetry already exists?
As the authors said - no more virtual envs.
A virtualenv is just a bunch of packages, you end up with the same thing whatever you want to call it. It is probably a more roundabout solution that it needs to be, but I don't find many problems myself (also using poetry).
Re: You don't really need a virtualenv
#8As a Ruby and Python developer I often wonder why Ruby doesn't need a virtual env. What did Ruby get right that Python didn't?
Or a lot of other languages...
Re: You don't really need a virtualenv
#9Earlier quoted context omitted.
As the authors said - no more virtual envs.
A virtualenv is just a bunch of packages, you end up with the same thing whatever you want to call it. It is probably a more roundabout solution that it needs to be, but I don't find many problems myself (also using poetry).
He also said virtual envs install their own copy of Python. No need for that either. Coming from other languages the whole virtual env thing seems alien especially the way it messes with your shell.
Re: You don't really need a virtualenv
#10This was a good article and looks like an interesting project. Regardless of whether or not you choose to _deploy_ with Docker, _developing_ in Docker containers using the VS Code Remote extensions really solved all of Python's (and Javascript's) annoying packaging problems for me, with the bonus that you also get to specify any additional (non-Python) dependencies right there in the repo Dockerfile and have the deve…
I do most of my development in docker. It's tricky to start but once you get the hang of it, it's fantastic. My goal is to one day roll something like RancherOS and provision my entire desktop environment in containers. Then you can just pick up and move it to whatever machine you wish.