I did start with a clean install of both web2py and Python 2.5. The reason why I'm "downgrading" (so to speak) to 2.5 is because I'm planning on running my web app on Google App Engine, and GAE runs on Python 2.5.2.
I know that Ubuntu 11.04 comes pre-installed with 2.6 and 2.7, so I had to manually compile and install 2.5 from source. I tried to run a fresh instance of web2py extracted from the zip file with 2.6 and 2.7 afterwards, and they both failed with the same error, which leads me to believe perhaps the error is elsewhere and is not Python/web2py related. Given the context of the errors, could it be at the database layer? And if so, what would be a good approach to unearth the underlying problem caused by the db connection? On Oct 6, 1:00 pm, pbreit <pbreitenb...@gmail.com> wrote: > I'd suggest starting over with a clean install if possible. Is there some > reason you are installing 2.5? If not, I'd avoid it and use what your server > comes with. > > I use Ubuntu 10.04 which is a "long term support" release and comes with > Python 2.6. But 11.04 should work fine, too.
