I very much appreciate this kind of feedback. My support of web2py has been slow but it has not needed much. The fact is, if you are using python 2.7 with web2py my ability to improve web2py is limited by the python version before anything else. Moving from web2py + 2.7 to web2py + 3.11 is a relatively small change for users.
I would very like to understand better how we can make py4web better and easier than web2py. On Sunday 25 August 2024 at 08:34:56 UTC-7 Peter wrote: > I am not a professional developer and I understand others have to consider > far greater risks in terms of any possible impact of errors and downtime > but I wanted to add my two pence (cents) worth regarding my experience of > upgrading to web2py to Python3! > > In 2016/17 I developed a web2py app for a family member to manage > activities, invoices, payments and more for a small business (sql db, > outgoing sms, pdf invoices/receipts... and hosted on pythonanywhere.com). > The app has been in use ever since with additions and modifications being > made periodically. In November 2022 I migrated the app to a new server (US > to EU but still pythonanywhere) and took the opportunity to upgrade to > python3. I found the upgrade to be a relatively painless exercise. As > Massimo mentioned there were some print statement errors and two maybe > three others that popped up. I found fixes for each error easily and they > were quickly corrected. > > Many thanks again Massimo and to all the support community for all the > work put in to web2py and py4web! > > Lastly, for what its worth, I have found py4web a bit more > advanced/intimidating to get started with but still would love to get > something useful up and running... 2025 might be the year! > > Peter > On Sunday 14 July 2024 at 03:10:05 UTC+1 Massimo Di Pierro wrote: > >> Hello everybody, >> >> You may have noticed I am not very active on this mailing list. That is >> mostly because I have been concentrating my energy on py4web which I think >> is must more modern and faster than web2py. >> >> Once again I want to encourage you to move. >> If you look at this page >> >> https://py4web.com/#why >> >> You will find it to be very familiar: >> - has an admin interface (called _dashboard) >> - has an dbadmin interface >> - same pyDAL >> - same template language >> - same helpers >> - same session interface >> - similar but better Form >> - similar but better Grid (still evolving) >> - different request object but compatible with bottlepy >> - different auth logic but support for more Oauth2 services (github, >> okta, facebook, etc.) >> - different but similar background scheduler >> >> Here are some instructions about how to move from web2py to py4web >> >> web2py currently works for python2.7 and python3.7+ but they are using a >> frozen version of pydal. This no longer works on Google App Engine. So how >> do we fix it? >> >> I am considering the following: >> - freezing web2py for Python 2.7 and stopping support. >> - continuing limited support of web2py for python3.7+ and specifically >> upgrade pydal for the lastest. >> - upgrade pydal so that it continues to work on Google App Engine for >> both web2py and py4web. >> >> My questions are: Is this worth it? Have people moved from python2.7 to >> 3.7+ already? Are people here interested in continuing to use web2py with >> GAE? >> >> >> Massimo >> >> >> >> -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/3aa85fac-e27e-4c7d-951c-a15d1e0b46cdn%40googlegroups.com.
