Re:Use pew, not virtualenvwrapper, for Python virtualenvs
by rye-neat on Friday September 08, 2017 @03:57PM
(#15203460)
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?
[ Parent
| on HN ]
Re:Use pew, not virtualenvwrapper, for Python virtualenvs
by lgunsch on Friday September 08, 2017 @04:20PM
(#15203610)
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.
Re:Use pew, not virtualenvwrapper, for Python virtualenvs
by BerislavLopac on Friday September 08, 2017 @04:49PM
(#15203829)
Virtualfish is amazing: https://github.com/adambrenecki/virtualfish
Re:Use pew, not virtualenvwrapper, for Python virtualenvs
by lgunsch on Friday September 08, 2017 @05:52PM
(#15204217)
Yeah, it works really well. That is what I use for my fish shell.
Re:Use pew, not virtualenvwrapper, for Python virtualenvs
by asddddd on Friday September 08, 2017 @04:50PM
(#15203842)
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.
Re:Use pew, not virtualenvwrapper, for Python virtualenvs
by yedpodtrzitko on Friday September 08, 2017 @04:23PM
(#15203627)
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.
Re:Use pew, not virtualenvwrapper, for Python virtualenvs
by gjjrfcbugxbhf on Friday September 08, 2017 @04:29PM
(#15203685)
Just use virtualenv