[pylons-discuss] Re: Porting a ZOPE (2.13) application into PYRAMID

+1 to the advice above on a gradual migration via failovers or "strangler" One method that once worked well for me in the past: viewing everything as a Service Oriented Architecture and extending the old system with new routes that enabled it to be the Auth/Login component for the new system.

Re: [pylons-discuss] Porting a ZOPE (2.13) application into PYRAMID

may be a little OT here, still worth a read in this context https://www.martinfowler.com/bliki/StranglerApplication.html On 19 September 2017 at 15:10, Brian Sutherland wrote: > On Thu, Sep 14, 2017 at 11:05:17PM +0300, Mikko Ohtamaa wrote: >> Hi Roberty, >> >> You are

Re: [pylons-discuss] How do I "forward" requests and switch their contexts?

Hi Jens, I would try to factor out as many code as possible which is common to both views into a separate function and use this function both context. I assume the validation and setting values in the profile work in the same way and does not rely on its context. This way you can implement