On 10/26/07, Christoph Haas <[EMAIL PROTECTED]> 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. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
