I am trying my best to release an alpha version by the end of April. My guess it will take a few more months to converge to a final product. One my goal is to move most of the template/grid/form logic client-side. That will be one of the main changes. I am unsure whether to backport the SQLFORM stuff but it would not be hard to do.
On Friday, 14 April 2017 02:15:49 UTC-5, Karoly Kantor wrote: > > I know this has been discussed before, but I really would like to have an > up-to-date perspective on this. > > I am currently developing an application in python 2.7, web2py 2.14.6 on > Google App Engine, that I plan to release for commercial use in September, > 2017. > > My short question is: should I stick to my current python and web2py or > should I switch to something newer now? > > Reasons behind the question: > - I understand python 2.7 will come to an "end of life", and python 3 is > not fully compatible > - GAE now supports python 3 > - I am not sure web2py is python 3 compatible, or it ever will be? > - I understand there is work on a "web3py", which might also not be > backwards compatible (?) > I would rather make a switch right now, if necessary, rather than after my > commercial golive. > > I would like to have an overall strategy on this, to see what's ahead in > the next few years. Any insights would be greatly appreciated. > > Greetings to all from Budapest, on a very nice sunny Good Friday :-) > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
