I would like to move from Pylons 1.0 to Pyramid, but I'm not going to be able manage a wholesale port any time soon. So, I'm wondering if it would be practical to start using some parts of Pyramid within an existing Pylons project.
In particular, one of the problems I'm having with Pylons is with configuration extensibility. I've got something working, but it feels clunky and is somewhat confusing. I haven't looked too closely at Pyramid, but it seems like its config system makes gathering & merging config from various locations a bit simpler. Has anyone done anything like this? Would any of the devs be able to advise on whether this an idea worth pursuing? -- 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.
