Good point about the fact web2py is fullstack... It could help in regard of appliance though?
Richard On Tue, Dec 8, 2015 at 12:05 AM, Massimo Di Pierro < [email protected]> wrote: > You see. we do not need that. Because we do not have a fragmented > ecosystem like Flask or Django made of many separate parts maintained by > different people. > Web2py has many more built in features and we make sure all the pieces > work together by shipping them together. > > Massimo > > > On Monday, 7 December 2015 20:54:19 UTC-6, Richard wrote: >> >> I fall on this : >> >> https://github.com/pocoo/metaflask >> >> It interesting. >> >> Richard >> > -- > 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. > -- 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.
