Hi All,
This is particularly problematic when using the common case of
SQLAlchemy declaratively mapped model classes.
The attached unit test when run will fail with:
Error in test test_provideAdapter (test_sa.TestAdapter)
Traceback (most recent call last):
File
On Fri, Feb 25, 2011 at 12:05, Laurence Rowe l...@lrowe.co.uk wrote:
I take that back, that documentation is incorrect, they have indeed
stopped working.
You are allowed to catch them, but not raise them. This is so you can
have code that runs on old Pythons with old libraries still.
But in
Summary of messages to the zope-tests list.
Period Sat Feb 26 12:00:00 2011 UTC to Sun Feb 27 12:00:00 2011 UTC.
There were 92 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 31 from
buildbot at winbot.zope.org, 11 from ccomb at free.fr, 5 from ct at gocept.com,
33 from jdriessen at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/27/2011 06:24 AM, Chris Withers wrote:
This is particularly problematic when using the common case of
SQLAlchemy declaratively mapped model classes.
The attached unit test when run will fail with:
Error in test test_provideAdapter
On 27/02/2011 17:22, Tres Seaver wrote:
TypeError: 'DeclarativeMeta' object is not iterable
Why is that and how should I register an adapter against such a class?
UTSL: the 'required' argument passed to 'registerAdapter' is supposed
to be a sequence of interfaces or classes, not a single
On 2011-02-25 21:56:49 +0100, David Glick said:
On 2/20/11 1:32 AM, Christian Zagrodnick wrote:
On 2011-02-19 17:17:44 +0100, Hanno Schlichting said:
On Thu, Feb 17, 2011 at 8:27 AM, Christian Zagrodnickc...@gocept.com
wrote:
On 2011-02-16 22:22:53 +0100, Hanno Schlichting said:
