Hi, I agree to what *vinyldarkscratch * wrote on Github*: "*Since all the Python 2/3 compatibility has already been implemented in gluon/_compat.py, there's hardly any additional work for cross-version support, at least that I can see. ". In my limited experience (making the web2py-manual official app compatible with PY2 and PY3), once you've learned how to use io.open and _compat.py it's quite easy to make old apps compatible with PY3 while retaining PY2 compatibility. And I'm certainly not a professional developer ;-) So, for the web2py framework itself all the work has already been done - kudos to all the contributors! For future bug fixes and improvements, the effort to fix it also for PY2 takes a fraction of what is needed to manage and debug +test two dedicated code bases. This is really a nightmare. For old applications, it's up to their creators. The path to the future is clearly to make them cross-compatible until they'll be able to totally switch their systems to PY3. For new applications that want to survive, PY3 is quite mandatory nowadays.
Anyhow, I agree hat we should better support python3 in any ways. For example, a lot of help is needed to rewrite and check the official manual. Also, for new users, we should strongly suggest to use python3 only. For helping with this, I've already opened the issue #2027 <https://github.com/web2py/web2py/issues/2027> in order to have binary versions of web2py with python 3.x included. Cheers, Nico Il giorno gio 31 gen 2019 alle ore 21:20 Eric <e.christiaa...@gmail.com> ha scritto: > Hi, > > I'm happily using Web2Py, but with the end of PY2 on 01-01-2020 ( > https://pythonclock.org) I'm curious why all the efforts are in place to > keep creating a version of Web2Py that supports PY2 and PY3 in one version? > Why not update the master only for PY3 stuff (remove the PY2 stuff?) and > create a specific PY2 branche with fixes/updates? > > I have the feeling this will make new/further development a lot easier > since PY2 is quickly left alone. > > Thanks for the reaction and keep up the nice work! > > > P.S.: I've started this post also on Git > <https://github.com/web2py/web2py/issues/2087>, but on advice of ilvalle > I've started the "discussion" here. > > -- > 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.
