Re:Python Packaging: Hate, hate, hate everywhere
by pyre on Friday June 22, 2012 @06:23PM
(#4149156)
virtualenv => a way of isolating a set of python libraries.
Sort of like a chroot for Python libraries.
(Python's version of Perl's perlbrew or Ruby's
rvm)
pip => Supercedes easy_install, but as this post mentions,
doesn't cover 100% of the use-cases (just the most
common ones). Think of it as Python's version of
Perl's cpanminus (aka cpanm).
burrito => The README says it all:
With one command, have a working Python
virtualenv + virtualenvwrapper environment
virtualenvwrapper => A set of shell scripts/functions for
working with multiple virtualenvs in
development. Basically sets them all up
in a central location so that you can
do things like:
workon my-websight-library-set
Re:Python Packaging: Hate, hate, hate everywhere
by aaronh on Saturday June 23, 2012 @02:26AM
(#4150224)
how is nobody aware of PythonBrew? to me it seems like the best and most comprehensive environment manager. it supports separate Python versions as well as virtual envs, in a very simple command line interface that is reminiscent of Ruby's RVM:
Re:Python Packaging: Hate, hate, hate everywhere
by pyre on Saturday June 23, 2012 @03:28AM
(#4150323)
I have heard of pythonbrew[1][2][3], but I didn't feel the need to list everything.
[1] http://news.ycombinator.com/item?id=3183721 [2] http://news.ycombinator.com/item?id=2795333 [3] http://news.ycombinator.com/item?id=2856131
I'd like to fix it too, but honestly I don't think people would adopt my package manager if I were to create something new from scratch.