On Sat, May 24, 2008 at 6:37 AM, rcs_comp <[EMAIL PROTECTED]> wrote: > > Hello all, > > I am new to the Python web-programming world and trying to decide on > frameworks. I was really impressed with Django, but ran into some > problems with IIS hosting. Since Pylons had really nice install > instructions for IIS, I started to take a look and I like the > philosophy. The WSGI from the ground up mentality seems to be a real > plus. > > However, I have run across a show stopper for me with Pylons unless I > have missed something in the documentation. Does Pylons support some > kind of module/plugin architecture that will allow me to develop "plug- > in" functionality across Pylons projects? What would be called in > Django an "app". > > For example, I would like to have a "news", "blog", and "calendar" > module that I can plug into different applications. The goal is to > have everything for the module contained in one subdirectory including > any configuration, routing, templates, controllers, model, etc. So, > something like this: > > /modules/news/... > /modules/calendar/... > /modules/blog/...
You can make a Pylons application for each component, and then tie them into the parent app via a pseudo-controller. (I.e., replace the controller class with your WSGI app instance, but keep the controller name.) Set full_stack=False in the subapplication; you may also want to comment out the error middleware. I haven't seen anyone do it but it theoretically should work. You may have to a little bit to pass the config dict. -- 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 -~----------~----~----~----~------~----~------~--~---
