13 messages in com.googlegroups.pylons-discussRe: Packages to use on Gutsy
FromSent OnAttachments
Matt Feifarek25 Oct 2007 13:37 
Garland, Ken R25 Oct 2007 13:41 
Ian Bicking25 Oct 2007 13:46 
Mike Orr25 Oct 2007 14:24 
Matt Feifarek26 Oct 2007 00:12 
Thomas Sidwick26 Oct 2007 00:44 
Christoph Haas26 Oct 2007 06:41 
Matt Feifarek26 Oct 2007 08:05 
zunzun26 Oct 2007 09:43 
Christoph Haas26 Oct 2007 11:59 
Mike Orr26 Oct 2007 14:22 
Christoph Haas26 Oct 2007 14:37 
Mike Orr26 Oct 2007 14:50 
Subject:Re: Packages to use on Gutsy
From:Mike Orr (slug@public.gmane.org)
Date:10/26/2007 02:50:05 PM
List:com.googlegroups.pylons-discuss

On 10/26/07, Christoph Haas
<email-Nf+wZpSdgwd6//Dw7l@public.gmane.org> wrote:

Formerly I was a fan of using the system-wide Pylons version. But I had to agree that this would break Pylons applications that rely on 0.9.4 and are suddendly faced with new version and might break.

Does this mean Pylons should be more careful about specifying which version of Pylons an app was created for, and using pkg_resources.require to activate the proper version? This would allow multiple Pylons apps to simultaneously use different versions of the system-wide libraries.

What makes it easier for me is, Pylons is the *only* Python package I use that has a lot of dependencies, so i know that anything unknown in /usr/local/lib/python2.5/site-packages is probably for Pylons. I do use global Python packages on my production system because all my apps are happy with the current versions. But if I had to install several apps, each with a large number of different dependencies, or I start getting version skew between what one app needs and another app needs, then I would start using virtualenv again. (Actually I haven't used virtualenv itself, just workingenv.) And Plone gets its own Python and own library directory.