I couldn't find the numbers that quickly, but key point is the bigger Flask community and plugin availability. Also if people look for job for companies that use python most of the time they look for Flask or Django experience.
Web3Py build on Flask would also remove the questions for beginners if they should use Flask or Web3py in which case they will most likely start with Flask. With Web3py having a flask component but the added value of pydal, yatl, sqlform and web2py Auth they would go for Web3py for sure. Now I perfectly understand however, that Web3py based on bottle would have a higher potential to be its own thing and find a community of its own and possibly even increase interest in all its moving parts such as bottle in reverse. And also effectively reducing the risk of Web3py being seen as just an extension as it could possibly happen with Flask, but actually being seen for what it is: much more than its moving parts combined. I guess it depends which end goal is more desirable. On Sun, 7 Apr 2019, 06:32 Massimo Di Pierro, <massimo.dipie...@gmail.com> wrote: > I like bottle because it is simpler than flask. Can you make a good case > for why Flask over bottle? > > On Tuesday, 2 April 2019 00:56:31 UTC-7, Kevin Keller wrote: >> >> Here is a project that generates swagger(openapi) documentation for >> flask+sqlalchemy. https://github.com/thomaxxl/safrs >> I was already wondering about changing bottle with flask, but I dont know >> if that is heresy now :). >> >> On Tue, Apr 2, 2019 at 9:31 AM Kevin Keller <keller...@gmail.com> wrote: >> >>> >>> https://editor.swagger.io/?_ga=2.227432986.689200959.1554189909-55439989.1547630410 >>> >>> >>> Swagger JSON editor + https://swagger.io/specification/. So one Swagger >>> Json file can contain the description of all the endpoints. >>> >>> On Tue, Apr 2, 2019 at 9:19 AM Kevin Keller <keller...@gmail.com> wrote: >>> >>>> I agree. >>>> >>>> In fact, the whole client side today should be Javascript and just >>>> communicate via REST+JWT (even though in the enerprise space you will also >>>> need OAUTH2). >>>> >>>> The models need to be exposed via REST easiliy and it should be easy >>>> to add auth to routes with JWT. Also the REST endpoints once defined, need >>>> to generate openapi(swagger) documents automatically. >>>> >>>> This is much like the JSON route you wanted to go, but with openapi we >>>> would be using an actual standard and do not tie ourselves to one >>>> Javascript framework and once specific JSON format. >>>> >>>> With that we could use something like this: >>>> https://api-platform.com/docs/client-generator/ that generates Vue.js >>>> or React.js CRUD pages basted on teh openapi documentation for the REST >>>> endpoints. >>>> >>>> On Tue, Apr 2, 2019 at 8:58 AM Massimo Di Pierro < >>>> massimo.dipie...@gmail.com> wrote: >>>> >>>>> Th problem with SQLFORM is that different CSS libraries require >>>>> different HTML stuctures. It is not as simple as selecting a class or div >>>>> vs span. In web2py we have code to deal with bootstrap 2 and 3. We apply >>>>> both classes. It is horrible. We should move away from generating html >>>>> server side for forms. We should pass a json description and generate it >>>>> client side >>>>> >>>>> On Sunday, 31 March 2019 00:54:23 UTC-7, 黄祥 wrote: >>>>>> >>>>>> Backporting SQLFORM, grid and Auth, should not be that complicated, >>>>>>> although I think we can do better. >>>>>>> >>>>>> >>>>>> sqlform, grid and auth is a great helper to make web2py as rapid >>>>>> application development, but please consider some of users who want to >>>>>> use >>>>>> another css or js framework. >>>>>> perhaps just follow the python principle 'Explicit is better than >>>>>> implicit', something like >>>>>> sqlform(), sqlform.grid() or form() signature have style='bootstrap', >>>>>> or class='something' or tag='div|span|table|tr|td' >>>>>> not sure just an idea >>>>>> perhaps can stick with the initial idea >>>>>> ref: >>>>>> https://groups.google.com/forum/#!msg/web2py/89a846kPeGA/nUpNJB_VCAAJ >>>>>> >>>>>> best regards, >>>>>> stifan >>>>>> >>>>> -- >>>>> 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. >>>>> >>>> -- > 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. > -- 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.
