On Nov 6, 1:46 pm, Jeff Tchang <[email protected]> wrote: > As a long time user of Pylons the thing that scares me is migration. > How much work is it going to take to get my Pylons 9.7/1.0 project to > Pyramid. Also since I have projects currently being worked on in > Pylons how much of this is going to be dead end work?
http://cd34.com/blog/framework/pylons-1-0-to-pyramid-1-0a1/ I had an undeployed Pylons 1.0 project that we had started working on about three weeks ago. We used repoze.who/repoze.what (I do not have Pyramid's auth working with an SQL backend yet) and FormAlchemy along with a number of webhelpers for pagination and constants. It took about 16 hours to convert 35 actions in three controllers to Pyramid. Of that 16 hours, I'd guess that 12 hours was learning Pyramids, reading the documentation, learning how Pyramid did things - I had looked at repoze.bfg in the not too distant past, and getting pointers on IRC to documentation and methodologies behind Pyramid. With that said. Pylons 1.0 isn't going away for a long time. It probably won't see many feature upgrades but will receive bugfixes for stability/security. I don't think I would worry about a project currently using 0.9.7/1.0 being orphaned and unsupported. While Pyramid is tagged as an Alpha release, it is a very mature Alpha. I do believe that we'll be using Pyramid for new development and as we work out some of the pitfalls we run into, I'll post the solutions we find. -- 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.
