4 ms·
I haven't used Poetry and most of my workplaces have done their own thing with versioning Python packages. So my virtualenv experience has been on my own or wit
by pfranz 6y ago
I haven't used Poetry and most of my workplaces have done their own thing with versioning Python packages. So my virtualenv experience has been on my own or with toy projects.
I really like writing one-off or sporadically used commandline tools. Loading a virtualenv or navigating to a directory before executing kind of sucks. Generally, I install into my homedir. I haven't read through or tried this out, but it seems like it might better address this use case.
You're right, this seems to be very similar. To me, it looks like it removes one abstraction layer of pushing-popping the environment.
- renewiltord 6y agoI have recently found Golang to be a good alternative. I too like Python and still write lots of scripts in it merely out of familiarity.
- teraku 6y agoYou can execute the python binary inside the venv's bin/ folder directly. But you still need the full path I guess
- pfranz 6y agoYou could add that bin/ to your PATH, but you'd also need something else to load the venv before executing it. You could write a generic wrapper that would load the env and call the Python binary and put that in a more generic bin/, but that's the kind of thing this proposal seems to make irrelevant. Another issue with wrappers is how quickly it executes. It's not a big deal for most executions, but for --help or building up a command pipeline it's really annoying to wait a second or two on each execution. That slow startup time also shows up when you start integrating it into automated processes.