Unless there'll be a release fixing this soon-ish: Is there any workaround
that doesn't require patching the sqlalchemy to avoid the issue?
Otherwise I'd probably go for a hack like this:
@contextmanager
def dirty_hack():
orig = sqlalchemy.orm.properties._orm_full_deannotate
sqlalchemy.orm.properties._orm_full_deannotate = lambda x: x
try:
yield
finally:
sqlalchemy.orm.properties._orm_full_deannotate = orig
and then wrap the creation of the column property in this contextmanager.
But I don't know whether skipping the deannotate step might cause other
issues...
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
