On May 26, 11:27 am, Mike Orr <[email protected]> wrote: > On Wed, May 26, 2010 at 11:05 AM, Mike Orr <[email protected]> wrote: > > As for Pylons' dependencies (this is off the top of my head and may > > not be 100% accurate): > > > - Beaker: optional (activated in middleware.py) > > - decorator: optional, required for ``pylons.decorator`` utilities > > - FormEncode: optional > > - Nose: optional, required for tests > > - Paste: required > > - PasteDeploy: required, Pylons uses some utilities internally (asbool) > > - PasteScript: required, for "paster create" etc. > > - Routes: required. (Strictly speaking, RoutesMiddleware or a > > compatible alternative is required) > > - simplejson: optional, required for ``pylons.decorator`` utilities. > > (Included in Python 2.6.) > > - Tempita: required by Paste > > - WebError: required? (May be deactivated in middleware.py?) > > - WebHelpers: optional > > - WebOb: required > > - WebTest: required? Required for tests. > > Moving all the optional dependencies to the application would cause > Pylons to have some undeclared dependencies. For instance, > ``pylons.decorator.*`` is not required for Pylons to run. But if > somebody tries to use some of the utilities in it, they'll get an > ImportError.
Moving only the dependencies that are never imported in the Pylons source makes sense to me, and perhaps some of the existing dependencies can be (re)moved too. Another option might be to make use of the `extras_require` setuptools functionality, but that can be hard for new users to grok also. -- 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.
