+1 agreed..... Lets remove some pressure from Massimo... Too much noise can harm the baby...
2017-06-12 15:03 GMT+01:00 Richard Vézina <ml.richard.vez...@gmail.com>: > Karoly, > > 1) Massimo had already mention that web2py will be supported by the core > team. You should know that core team much more involve in the maintenance > and enhancement of web2py lately than Massimo is. I am rely confident in > the maintenance of web2py for a fading out period if web3py will get > traction. If web3py don't get traction, I am pretty sure that web2py will > still continue to have a large user base and good core team to at least > keep thing working. > > 2) Only Massimo can answer that, but I am confident that it will consider > this aspect, clear and easy path to transition from w2p to w3p... So there > should be a simple way to refactor your app to migrate it to web3py. But > web3py will brake backward compatibility, so you have to expect to have > major refactoring to do what exactly will be known when the time comes. > > Richard > > On Mon, Jun 12, 2017 at 3:39 AM, Karoly Kantor <kar...@kantor.hu> wrote: > >> >> >> For people to feel they have an understanding on the web2py roadmap and >> trust in in its future, i think it would be important to get clear answers >> to the following questions: >> >> 1. When "web3py" is released, what will happen to web2py? Will it come to >> an end of life, or will the two frameworks continue to be maintained >> parallel? >> >> 2. What will be the relationship between web2py and web3py? I would guess >> that contributors' efforts will shift to web3py, so what happens to >> existing web2py based applications? Will there be an upgrade path with >> reasonable effort, of will those apps be stuck with an old framework from >> which contributor effort has shifted away? >> >> >> >>> >>> Just to be clear, web2py 2.15.1 will be released in the next few days >>> and will support Python 3. It is still web2py, just with Python 3 support >>> and a number of other updates and fixes. web3py will be a completely >>> new framework (also supporting Python 3), quite different from web2py. It >>> is not close to ready for release. >>> >>> Anthony >>> >> -- >> 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.
