On Tuesday, May 30, 2017 at 2:54:28 PM UTC-7, icodk wrote: > > Could be interesting to hear what are the arguments for the porting >
The porting for what? Porting web2py to Python3? Porting web2py to web3py? Porting web2py apps to web3py? Problems with compatibility [and eventually, Py2 EOL] are the arguments for porting web2py to Py3. Massimo has a recent message [re-]stating his reasons: web2py bloat, especially in the forms area; better support of microapps and response client code, and performance improvements. Porting of individual apps to web3py will only make sense when they run into a limitation of web2py that the newer code has a better way of dealing with, or when web2py maintenance costs too much in terms of volunteer time or availability of the parts needed. You should be able to find more by browsing the group archives. /dps > On Tuesday, May 30, 2017 at 8:41:38 AM UTC+2, T.R.Rajkumar wrote: >> >> I am now porting a jsp application to web2py. Should I stay with web2py >> or wait for web3py? Will there be web2py group support like now after >> web3py. Pl guide. Thanks. >> > -- 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.
