You can use SQLAlchemy with it as you can use any Python package you like but...
1) The web2py DAL is designed to work with SQLFORM. SQLAlchemy is not. By using SQLAlchemy you would be using web2py more or less like you would use Pylons, thus missing a lot of the extra stuff that web2py does for you (and that you do not see because you think SQLAlchemy).
2) It is internal DAL is comparable and in some cases better than SQLAlchemy because is smaller, faster, and it works on the Google App Engine. By using SQLAlchemy your web2py programs would not run on GAE.
3) web2py users like the web2py DAL better than SQLAlchemy. That is why hey use web2py.
We are not reinventing the wheel. We are just building a better wheel that runs faster and is easier to spin. We are not reinventing the wheel any more or less than any other framework did.
Comments
You can use SQLAlchemy with it as you can use any Python package you like but...
1) The web2py DAL is designed to work with SQLFORM. SQLAlchemy is not. By using SQLAlchemy you would be using web2py more or less like you would use Pylons, thus missing a lot of the extra stuff that web2py does for you (and that you do not see because you think SQLAlchemy).
2) It is internal DAL is comparable and in some cases better than SQLAlchemy because is smaller, faster, and it works on the Google App Engine. By using SQLAlchemy your web2py programs would not run on GAE.
3) web2py users like the web2py DAL better than SQLAlchemy. That is why hey use web2py.
We are not reinventing the wheel. We are just building a better wheel that runs faster and is easier to spin. We are not reinventing the wheel any more or less than any other framework did.