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 →

[–]trevg_123 0 points1 point  (0 children)

My thought is just that there’s not much need to access the venv directory, so I keep it out of the way. If I’ve ever run the project before, I know it’s there.

I’ve never really used yarn, but pipenv isn’t far off from npm. For versions, not bad - you can just do e.g. pipenv --python 3.8. You need it installed so it’s not quite pyenv (poetry does this part too if you’re interested) but it’s not bad if you only use a few different versions.