Migration to Python 3 aside (which has to happen, sooner or later) my concern here is that moving to Pyramid 2 so quickly is a bit premature given the paint is barely dry on Pyramid 1.
Should we not wait until there are some actual projects built with Pyramid, and we get feedback from real world usage ? The danger is that this ends up like TG2 - a continually moving target moving from one dependency to the next, depending on what's flavour of the month, with a small core of developers continually making changes but leaving behind those who need a stable framework to work on. I would suggest that any major changes to Pyramid should depend on what users actually want or need. Yes, YAML may be better than INI. But it's not something that people using Pyramid have any issues with at this point. Ditto moving bits hither and thither from Paste. People coming to Pyramid are already having issues understanding differences between URL dispatch and traversal, authentication, testing etc. That's OK as Pyramid is a low-level framework and the higher-level stuff is still being built on top of it. But to add yet another slew of huge and fundamental changes will confuse and turn away people from Pyramid altogether. -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
