Massimo, Do you see its better to do incremental changes to web2py that leads us to web3py at some point than to a completely new framework which may be lot of work and it will take monumental effort to fix all the bugs it may have.Just some thoughts...
On Tuesday, May 30, 2017 at 12:40:45 PM UTC-4, Marlysson Silva wrote: > > Could you put this thoughts about web2py's future in some place to > community? In issues , documentation , topic discussion .. > > So the community would know what have to do and could suggest more > enhancements .. > > Because the people stay waiting by some programmers to develop some > features of framework.. and showing to others programmers and discussing, > they could help. > > > Em terça-feira, 30 de maio de 2017 07:38:23 UTC-3, Karoly Kantor escreveu: >> >> Hello Massimo, May I have two questions on this? >> >> 1. You say current web2py interprets code on every request. What does >> this mean on Google App Engine? (Every time I deploy, GAE seems to >> compile...) >> >> 2. Overall, what do your plans exactly mean for people with an existing >> app on web2py? Is this a brand new and different framework or is there an >> upgrade path? >> >> 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
