I actually moved from web2py to Flask and Flask-SQLAlchemy as my framework of choice because of the limitations imposed by the web2py DAL (try modeling a school, for example, with the relationships between teachers, students, parents, and classes. It's very difficult in practice on the DAL).
The rest of the web2py framework is excellent, and support is very good. I wish Massimo had spent some of the time he spent adapting web2py to other frameworks on adapting web2py to SQLAlchemy instead. I'd be back in a second.
Sounds like FUD. Care to share some examples? Note, in most cases, the DAL has fewer, not more limitations than a typical ORM. web2py does use standard Python. What bad practices? Have you seen this: http://www.infoworld.com/slideshow/24605/infoworlds-2012-tec...?
> try modeling a school, for example, with the relationships between teachers, students, parents, and classes.
The DAL can be used to model any set of tables and relationships that can be created in an RDBMS, so it's not clear what the problem would be modeling the relationships among these entities. Should be fairly straightforward.
The rest of the web2py framework is excellent, and support is very good. I wish Massimo had spent some of the time he spent adapting web2py to other frameworks on adapting web2py to SQLAlchemy instead. I'd be back in a second.