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 Friday, April 24, 2015 at 5:07:58 PM UTC-7, Michael Bayer wrote: > > 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 4/24/15 7:02 PM, Bill Schindler wrote: > > 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 > "/opt/certwise-lcs/eggs/lcs.content.user-1.0.2dev_r10-py2.7.egg/lcs/content/user/makeorm.py", > > line 89, in make_orm > class Principals(Base): > File > "/opt/certwise-lcs/eggs/SQLAlchemy-1.0.1-py2.7-linux-x86_64.egg/sqlalchemy/ext/declarative/api.py", > > line 55, in __init__ > _as_declarative(cls, classname, cls.__dict__) > File > "/opt/certwise-lcs/eggs/SQLAlchemy-1.0.1-py2.7-linux-x86_64.egg/sqlalchemy/ext/declarative/base.py", > > line 87, in _as_declarative > _MapperConfig.setup_mapping(cls, classname, dict_) > File > "/opt/certwise-lcs/eggs/SQLAlchemy-1.0.1-py2.7-linux-x86_64.egg/sqlalchemy/ext/declarative/base.py", > > line 102, in setup_mapping > cfg_cls(cls_, classname, dict_) > File > "/opt/certwise-lcs/eggs/SQLAlchemy-1.0.1-py2.7-linux-x86_64.egg/sqlalchemy/ext/declarative/base.py", > > line 134, in __init__ > self._early_mapping() > File > "/opt/certwise-lcs/eggs/SQLAlchemy-1.0.1-py2.7-linux-x86_64.egg/sqlalchemy/ext/declarative/base.py", > > line 137, in _early_mapping > self.map() > File > "/opt/certwise-lcs/eggs/SQLAlchemy-1.0.1-py2.7-linux-x86_64.egg/sqlalchemy/ext/declarative/base.py", > > line 530, in map > del mp_.class_manager.info['declared_attr_reg'] > AttributeError: 'NoneType' object has no attribute 'class_manager' > > This gets fired off on every ORM class, so I'm guessing the cause is > somewhere deeper in our code. Any thoughts on what I might look for to find > the cause? > > -- > Bill > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sqlalchemy+...@googlegroups.com <javascript:>. > To post to this group, send email to sqlal...@googlegroups.com > <javascript:>. > Visit this group at http://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
