Excerpts from Nick Coghlan's message of 2013-11-25 11:44:38 +1000:

SQL Alchemy 0.9 is switching the engine URL handling to comply with RFC 1738:

http://docs.sqlalchemy.org/en/rel_0_9/changelog/migration_09.html#the-passwo...

I don't think that change will impact Beaker directly, but it could potentially affect the required spelling of affected passwords in configuration files depending on the version of SQL Alchemy in use.

That's kind of annoying.

We could add a note to server.cfg explaining that the password should be URI-encoded if you have SQLAlchemy < 0.9. Other than that, I don't think we can do anything else about it on the Beaker side.