I would advise against the strategy of wrapping the Pylons application in a Pyramid view. I used to do this, but the dependencies in the python environment are now conflicting between Pylons and Pyramid. There are packages where the latest version of Pyramid requires a newer version than Pylons can use. One of the packages was WebOb, but I think there were other packages as well.
I currently have NginX in front of Pyramid and Pylons applications (running in Paste) and it decides based on the first path segment whether to go to the legacy app or the new pyramid application. This seems to be the easiest method for porting controllers one at a time. -- Jason -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-discuss/-/sDcxm3LAQXwJ. 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.
