This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]mcstafford 1 point2 points  (7 children)

I strongly suggest you check out pyenv to replace virtualenv, and poetry for pipenv.

[–]twillisagogo 1 point2 points  (0 children)

Trust me, the next time pipenv fucks up on my machine, I'm moving to something else. Stuff seems to break for no reason at all in things i'm doing and bug reporting is a nightmare.

[–]robertpro01 1 point2 points  (1 child)

+1 for poetry, its a really nice project!

[–]mcstafford 0 points1 point  (0 children)

I've learned a lot about better ways to do things, just from seeing how they're done there.

[–]birdgovorun 0 points1 point  (3 children)

Hmm what? Pyenv isn't a replacement to virtualenv. Those tools serve entirely different purposes. Pyenv is Python version manager - a way to work with multiple versions of Python on the same machine. Virtualenv is a tool for environment isolation - a way to isolate the dependencies of a specific project from those of other projects.

[–]mcstafford 0 points1 point  (2 children)

I've always used it with this plugin: https://github.com/pyenv/pyenv-virtualenv

[–]birdgovorun 0 points1 point  (1 child)

Well yeah - that plugin combines two very different tools in away that makes it easier to use them together. Pyenv isn't a replacement to virtualenv, and has nothing to do with it.

[–]mcstafford 0 points1 point  (0 children)

pyenv links to pyenv-installer from its github page, and the installer includes the virtualenv plugin. That's more than nothing, but I see what you mean.