Well, if you want to have something different, we would probably need to look into things like scaffolding of a web3py REST backend with oauth2+jwt security for the endpoints plus automatic openapi (swagger) documentation/files and a frontend based i,.e. on Vue.js or React/Angular. Somewhat similiar to JHipster. I suppose the decoupling of frontend javasript and backend python code is where the development of web pages is headed. That would also enable easy to create mobile applications with a web2py backend.
Other ideas are of course to develop the low code approach further, to have something like Oracle APEX https://apex.oracle.com/en/ or https://anvil.works/, which is a low code environment purely based on python including the frontend. While it uses sculpt which is only python2 comptabile, we could look and transcrypt if we had a visual environment were poeple can drag and drop elements and code their behaviour in python via transcrypt. https://www.transcrypt.org/ So I dont know where you thoughts were headed, but it is towards the future, then these are my 2 cents. Possibly low hanging fruit is to focus on easy REST API with automatic openapi documentation and then go from there. But if we are there, I suppose we are already at Web4Py, which is even a better sounding name. Web3Py, just to regain more popularity, but making it clear that web2py is fully python3 compatible and increase stability by further code reviews by more coders would be a good first step I thought. On Mon, Mar 18, 2019 at 3:47 AM Massimo Di Pierro < massimo.dipie...@gmail.com> wrote: > I think web3py should be something a little different, not just web2py for > python3. > > > > On Sunday, 17 March 2019 05:42:16 UTC-7, Kevin Keller wrote: >> >> Hey, >> >> So I was wondering today what you guys would think about the idea to >> rename web2py to Web3py, once it reaches a level of maturity that would be >> able to justify the rename and a reboot. >> >> That would also mean to update the web page and various resources. >> >> The reason is simple : >> >> It seems that since around 2016 python 3 has seen a major increase in >> adoption while web2py adoption decreased due to being perceived as python2 >> only framework, which at the time was certainly true. >> >> While it's not true anymore, I think the perception of being a python2 >> only framework combined with outdated resources doesn't help adoption. >> >> While sacrificing the established name is certainly not great, I think >> the benefits of a reboot with a name change to emphasize the python3 >> compatibility would far outweigh any drawback. >> Python2 compatibility that is maintained would however seen as a plus and >> a major differentiator to other frameworks that dropped python2 support. >> >> What do you think? >> >> -- > 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.
