Still getting the same error with 1.0.2.
It's using a custom base class passed to declarative.declarative_base().
The class is pretty simple -- mostly just a declared_attr to set the
__tablename__ and a custom __repr__.
I'll see if I can pare it down to a simple test case.
--
Bill
--
You
This may have been an instance of working by accident. In setting up
declarative_base, we're passing in a mapper function. Our mapper function
wasn't returning the result of the SA mapper(). It didn't cause any
(explicit) errors through 0.9.8, but I have a feeling that was just luck.
On
I'm trying to upgrade from SA 0.9.8 to 1.0.1 and getting a traceback. I'm
not sure what's going on here, but the declarative setup is obviously not
happy with something. (On 0.9.8, everything runs fine, so I've obviously
run afoul of something new/different/fixed.)
File
give 1.0.2 a try since we adjusted some things regarding
__declare_first__ and __declare_last__. Further than that it depends a
lot on what your basic Base setup looks like, mixins in use,
extensions like AbstractConcreteBase, stuff like that. Any details you
can share would help.
On
