+1 In a production system with thousands of lines of code, lots of servers, databases... I plan to keep the systems frozen (CENTOS 6, python 2.6 and web2py 2.x) for some years with the exception of security patches. The cost of reviewing/updating the existing code is too high... So web3py could be the next generation framework, and backward compatibility should be the principal goal from my point of view
Best regards On Wednesday, 28 November 2012 19:42:48 UTC+1, LightDot wrote: > > Age in weeks? ;) > > On a serious note, I plan to use web2py on RHEL 6 systems for another 5-8 > years. Once RHEL 7 is out, this new rewrite (web3py aka web2py 3.0 or > whatever will it become) will most likely be a viable replacement for new > projects, if it's released. I'm assuming web2py features and versatility > are a good indicator for the new project, although I haven't looked at the > code yet. Don't see any reasons to doubt. :) > > But, at least for me, web2py isn't going anywhere soon. > > Regards, > Ales > > On Wednesday, November 28, 2012 7:03:35 PM UTC+1, VP wrote: >> >> I have already put in my few cents in that thread. The only thing I >> want to say here is that I hope web3py will be out soon. I think web2py >> has started to show its age a little bit. >> >> :) >> > --
