[Beaker-devel] Possible config file compatibility issue for SQLAlchemy 0.9

Dan Callaghan dcallagh at redhat.com
Mon Nov 25 03:50:57 UTC 2013


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-password-portion-of-a-create-engine-url-is-no-longer-url-encoded
> 
> 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.

-- 
Dan Callaghan <dcallagh at redhat.com>
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <https://lists.fedorahosted.org/pipermail/beaker-devel/attachments/20131125/c1ab6ace/attachment.sig>


More information about the Beaker-devel mailing list