I would say the same , have no fear. I have application that run Pylons 0.9.7 and 1.0 and others that run different Webpy's versions, all under virtualenv. I can understand the fact that you've spent a lot of time understanding how Pylons works and you start feeling comfortable with, but at some point nothing can be the same for years to years, transformation is a natural process.
>From experience I can tell you that most of the time we start with something simple, grow to something more complicated, and switch to something else because at the time we made our choice, our understanding was not the same because we hadn't the experience. With this experience you have more ability to choose one framework or another based on requirement, timeframe, skills and budget. That said, what's really interesting in Pyramid is that you can use it the way you want because it has no opinion. It's a framework to build webapps but also to build framework. With it's different starter projects you can already use it the bfg way and a minimalistic pylons 2 way or use it as a single file app like here http://docs.pylonshq.com/pyramid/dev/narr/firstapp.html#hello-world-goodbye-world Just as an example, Chris McDonough created a simple Flask clone using repoze.bfg, http://bfg.repoze.org/videos#groundhog1 -- 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.
