Massimo, web3py,...
- Will it have a web interface? - Template: web2py template language? - How about default.py? How about all the queries we make to the database? The same method will apply? - It will a full scale battery included or a minimalist approach like flask or bottle? - All the plugins will still work? - How much of rework needed if someone wants to convert a web2py app to web3py? I am guessing if pydal and the template language is same then very minimal. Are you going to provide a conversion doc (conversion from web2py to web3py)? - Do you recommend people who are using web2py for deployment and regular site (already functionaly) to switch over to web3py and leave web2py just to get the training and that's it? - Is there a specific advantage of web3py over web2py other than speed? -Ron On Sunday, June 11, 2017 at 4:14:38 AM UTC-4, Massimo Di Pierro wrote: > > Speed depends on what the app does. Which template you use, which db, etc. > In general the bottle neck of any app is the database. > > That said most people like to benchmark on simple hello world apps without > sessions and templates. In this case web2py does not do well. web3py will > do as fast as Flask, faster than Django. > > On Friday, 9 June 2017 20:30:08 UTC-5, Ron Chatterjee wrote: >> >> No I am saying how fast web3py will be comparing django or flask? > > -- 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.
