On 10/25/07, Matt Feifarek <[EMAIL PROTECTED]> wrote: > Does anyone have a recommendation as to which portions of the Pylons > requirements are best to use via OS-level package management and which are > best to use via easy_install? It seems that most people favor an > all-or-nothing approach, but that's kinda not practical.
Definitely use easy_install for Pylons and its dependencies, because they are changing too fast for an OS to keep up with, and OSes have policies against including beta or development packages. Inevitably there will be a bug in Paste or Beaker or SQLAlchemy and the fix is only in the development version, or you'll need a brand-new feature. Having to switch from an OS package to an easy_install package in that case it a bit of a hassle, especially if that package is in the middle of a dependency chain. However, if a package has been around for at least a year and you're only using its basic features rather than some brand-new feature, it's fine to install it as an OS package. For me this means PIL, Cheetah, MySQLdb, docutils, etc. -- 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 -~----------~----~----~----~------~----~------~--~---
