Comments on: Don’t put all your Python eggs in one basket http://shazow.net/blog/2008/09/02/dont-put-all-your-python-eggs-in-one-basket/ The cake is a lie Fri, 03 Sep 2010 01:46:58 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: ZK@Web Marketing Blog http://shazow.net/blog/2008/09/02/dont-put-all-your-python-eggs-in-one-basket/comment-page-1/#comment-34838 ZK@Web Marketing Blog Sun, 24 May 2009 18:06:01 +0000 http://shazow.net/blog/?p=129#comment-34838 I can build a python instance that is independent of the stuff build into my main python (which is a virtual-python for historical reasons). It's better than virtual-python because I get the benefits of things in my system site-packages that I've installed since I installed my virtual python. I can build a python instance that is independent of the stuff build into my main python (which is a virtual-python for historical reasons). It’s better than virtual-python because I get the benefits of things in my system site-packages that I’ve installed since I installed my virtual python.

]]> By: shazow http://shazow.net/blog/2008/09/02/dont-put-all-your-python-eggs-in-one-basket/comment-page-1/#comment-18567 shazow Tue, 09 Sep 2008 19:53:53 +0000 http://shazow.net/blog/?p=129#comment-18567 @Chris you're right! --no-site-packages is a great idea, I just use this setup on my own single-user machines so it's not as much of a factor. It's definitely recommended for multi-version situations and production environments. I'll edit the post accordingly. Thanks! @Chris you’re right! –no-site-packages is a great idea, I just use this setup on my own single-user machines so it’s not as much of a factor. It’s definitely recommended for multi-version situations and production environments. I’ll edit the post accordingly.

Thanks!

]]> By: Chris Perkins http://shazow.net/blog/2008/09/02/dont-put-all-your-python-eggs-in-one-basket/comment-page-1/#comment-18566 Chris Perkins Tue, 09 Sep 2008 19:47:44 +0000 http://shazow.net/blog/?p=129#comment-18566 I am surprised you do not use --no-site-packages. I find this indispensable. I have done a short v-cast on how to create a virtualenv and use it effectively: http://showmedo.com/videos/video?name=2910000&fromSeriesID=291 I am surprised you do not use –no-site-packages. I find this indispensable. I have done a short v-cast on how to create a virtualenv and use it effectively:

http://showmedo.com/videos/video?name=2910000&fromSeriesID=291

]]> By: shazow http://shazow.net/blog/2008/09/02/dont-put-all-your-python-eggs-in-one-basket/comment-page-1/#comment-18451 shazow Tue, 02 Sep 2008 16:14:35 +0000 http://shazow.net/blog/?p=129#comment-18451 @Phillip Ah, thanks for the tip! Unfortunately, easy_install -m doesn't seem to cover the entire scenario. It does remove the entry from easy-install.pth, and it does print out what scripts it put into your bin directory, but it doesn't remove the egg from your site-packages, nor does it prevent overwriting of other binaries with the same name. As for using the multi-version mode, it doesn't really help you as much if the code in question does not use pkg_resources, but it is a step in the right direction. Overall, it's still better to have a separate user-local Python site-packages, but I will keep -m in mind. @Phillip Ah, thanks for the tip! Unfortunately, easy_install -m doesn’t seem to cover the entire scenario. It does remove the entry from easy-install.pth, and it does print out what scripts it put into your bin directory, but it doesn’t remove the egg from your site-packages, nor does it prevent overwriting of other binaries with the same name.

As for using the multi-version mode, it doesn’t really help you as much if the code in question does not use pkg_resources, but it is a step in the right direction.

Overall, it’s still better to have a separate user-local Python site-packages, but I will keep -m in mind.

]]> By: Phillip J. Eby http://shazow.net/blog/2008/09/02/dont-put-all-your-python-eggs-in-one-basket/comment-page-1/#comment-18442 Phillip J. Eby Tue, 02 Sep 2008 13:47:47 +0000 http://shazow.net/blog/?p=129#comment-18442 Actually, you use "easy_install -m packagename" to remove it from easy-install.pth... and that will also dump out for you what scripts need to be removed. Second, if you need multiple versions of an egg installed, that's what "easy_install -m" is for. You only need to re-run easy_install to change the *default* version - the one that comes up when the Python interpreter is started, not what comes up when you run a given project's scripts. Not that virtualenvs aren't great, but those two things don't require them. Actually, you use “easy_install -m packagename” to remove it from easy-install.pth… and that will also dump out for you what scripts need to be removed.

Second, if you need multiple versions of an egg installed, that’s what “easy_install -m” is for. You only need to re-run easy_install to change the *default* version – the one that comes up when the Python interpreter is started, not what comes up when you run a given project’s scripts.

Not that virtualenvs aren’t great, but those two things don’t require them.

]]>