Pylons to Pyramid Migration

[burgiduroy]

Are there any pylons to pyramid migration guide. How can I do this smoothly. 

Our app got about 50 controllers. Is it possible to migrate by batch? 

I'm thinking about running parallel instances of pylons and pyramid on the same server, and just do a redirect from pylons to pyramid.

Is this idea doable or are there any better approach tho this.

[Chris McDonough]

Here's one strategy:

http://docs.pylonsproject.org/projects/pyramid_cookbook/en/latest/porting/legacy.html

Here are some other suggestions:

http://docs.pylonsproject.org/projects/pyramid_cookbook/en/latest/pylons/migrate.html


>
> --
> You received this message because you are subscribed to the Google
> Groups "pylons-discuss" group.
> To post to this group, send email to pylons-...@googlegroups.com.
> To unsubscribe from this group, send email to
> pylons-discus...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/pylons-discuss?hl=en.

[Jason]

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