My Python Development Environment, 2018 Edition
jacobian.org
My Python Development Environment, 2018 Edition
1–10 of 224 posts
Re: My Python Development Environment, 2018 Edition
#2Why specifically do you use it instead of virtualenv (+virtualenvwrapper)?
Re: My Python Development Environment, 2018 Edition
#3Re: My Python Development Environment, 2018 Edition
#4>Why? pipenv handles dependency- and virtual-environment-management in a way that’s very intuitive (to me), and fits perfectly with my desired workflow. Why specifically do you use it instead of virtualenv (+virtualenvwrapper)?
Re: My Python Development Environment, 2018 Edition
#5>Why? pipenv handles dependency- and virtual-environment-management in a way that’s very intuitive (to me), and fits perfectly with my desired workflow. Why specifically do you use it instead of virtualenv (+virtualenvwrapper)?
Re: My Python Development Environment, 2018 Edition
#6>Why? pipenv handles dependency- and virtual-environment-management in a way that’s very intuitive (to me), and fits perfectly with my desired workflow. Why specifically do you use it instead of virtualenv (+virtualenvwrapper)?
Re: My Python Development Environment, 2018 Edition
#7Pyenv looks great! Sad I didn't know about this sooner, though I do have the luxury of using mostly one version of Python and have only confused it for the system Python once or twice.
Re: My Python Development Environment, 2018 Edition
#8 > source env/bin/activate
How does one activate one environment over another?Why is pipsi a separate thing?
Re: My Python Development Environment, 2018 Edition
#9>Why? pipenv handles dependency- and virtual-environment-management in a way that’s very intuitive (to me), and fits perfectly with my desired workflow. Why specifically do you use it instead of virtualenv (+virtualenvwrapper)?
It also, like pew, opens the virtualenv in a new shell instead of activating the current shell. A much saner approach.
The UI is also more user friendly: one entry point for everything, pretty colors and icons, auto-correct of package name, and so on.
Using Pipfiles, instead of requirements, are generally a better experience than requirements.txt since it contains dev and prod dependancies and allow separated dependancy pinning, with file hash.
Re: My Python Development Environment, 2018 Edition
#10pipenv
pyenv
mkvirtualenv
virtualenv
pipsi
venv
pew
conda
virtualenvwrapper
i'm sure i'm forgetting like 5.
this is like https://xkcd.com/927/
for the record i use pyenv and virtualenv (although playing with ML i'm using conda)