I'm wondering if it might be worth splitting Pylons into a PylonsCore package containing PylonsApp and the essential dependencies, and a Pylons shell package containing optional dependencies (Mako, Routes, simplejson). This would allow people who don't want optional packages installed to skip them without deleting packages that are formal dependencies (and would thus be reinstalled if somebody runs "python setup.py install" on the application). But most people would just install Pylons and continue as before.
A few issues with this are where to put the paster template (which depends on PasteDeploy), render_mako, @jsonify, etc. I would put them all in PylonsCore, even though they depend on undeclared packages. That would be easier than splitting modules between the packages or worse, splitting parts of modules between packages. -- Mike Orr <sluggos...@gmail.com> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
