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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/web2py/aaad81f2-7268-4ee3-9ffa-1f61289ab4bbn%40googlegroups.com.
