[rye-neat]

As someone who is finally getting into Python development (via Django) after following tons of tutorials over several years: should I be using pew, virtualenvwrapper, or something else? This article is from 2015, how relevant is it today?

[lgunsch]

Most people I've met use virtualenvwrapper. It doesn't work on other shells like fish though. However, I'd simply focus on learning how virtualenv works, and use whatever tool to manage it as you feel like.

[BerislavLopac]

Virtualfish is amazing: https://github.com/adambrenecki/virtualfish

[lgunsch]

Yeah, it works really well. That is what I use for my fish shell.

[asddddd]

It doesn't matter much, it's all just sugar over virtualenvs (which are quite simple conceptually). Virtualenvwrapper has been around a long time and works pretty well.

More recent tools are Pipenv (which I've been using) and hatch - I don't think there is any One True Way since the days of virtualenvwrapper being the latest and shiniest.

If you want a really easy to use tool that doesn't require any understanding of virtualenvs, I'd look at Pipenv.

http://docs.pipenv.org/en/latest/

[yedpodtrzitko]

I use Autoenv. It has one ultimate advantage - you don't need to learn any new tools/commands or execute anything manually. Also it's totally up to your decision where do you want to have the virtualenv. Just put a file `.env` with anything you want to execute automatically (eg. `source venv/bin/activate`) into your project directory, and that's it - it will run any time you'll `cd` or open a new shell there.

[gjjrfcbugxbhf]

Just use virtualenv

[baq]

i just use activate and tmux, i'm allergic to tools having an opinion about where my venvs should live.