[Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets

[Bitbucket <com...@bi...>]

3 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/8e10ab92df0d/
Changeset:   8e10ab92df0d
Branch:      None
User:        zzzeek
Date:        2014-03-23 00:02:37
Summary:     - restore the old behavior of the connection pool replacing itself just
within userland engine.dispose(); as some SQLA tests already failed when the replace step
was removed, due to those conns still being referenced, it's likely this will
create surprises for all those users that incorrectly use dispose()
and it's not really worth dealing with.  This doesn't affect the change
we made for ref: #2985.

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/a7a6b436600c/
Changeset:   a7a6b436600c
Branch:      None
User:        zzzeek
Date:        2014-03-23 00:10:00
Summary:     there's no "assert_call_count" on mock

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/b00e15b50f83/
Changeset:   b00e15b50f83
Branch:      None
User:        zzzeek
Date:        2014-03-23 00:34:18
Summary:     - An event listener can now be associated with a :class:`.Engine`,
after one or more :class:`.Connection` objects have been created
(such as by an orm :class:`.Session` or via explicit connect)
and the listener will pick up events from those connections.
Previously, performance concerns pushed the event transfer from
:class:`.Engine` to  :class:`.Connection` at init-time only, but
we've inlined a bunch of conditional checks to make this possible
without any additional function calls. fixes #2978

Affected #:  3 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.