Possible switch from venv to pipenv

[HeathNaylor]

In my experience, I have found it easier to both work with and teach pipenv over venv, would you be open to switching to that? I am looking to implement dotenv but don't want to double up on work if I can help it.

[briancappello]

Hey Heath, sure, I'd be open to using pipenv. I think it has the advantge of integrating with .env files natively (or at least I know it works with pipenv shell).

[briancappello]

I'm a little old-school and prefer mkvirtualenv myself, but I definitely agree about pipenv being a good default. Plus more advanced users that wish to use other tools can always do so on their own

[squarism]

My own two cents, we switched from requirements.txt to pipenv and that by itself was better. I didn't completely love the experience with having to drop into a shell and some other things. I looked at poetry (the README has a few opinions on pipenv) and I like it so far although it's been only a short amount of time. I agree/align with poetry's world view because it's similar to other languages' defaults/flow (my bias).

The only weird thing is the installer (curl+sh ... eh) but I'm using the pip installed version without issue.