I think that patch which you would like to provide could add
functools.wraps decorator to the decorator defined in synonym_for().
See http://docs.python.org/library/functools.html#functools.wraps
--
Anton Gritsay
http://angri.ru
On 12 июн, 22:20, Christophe de VIENNE cdevie...@gmail.com wrote:
dispatch. It can be
used not only with mapper's events but also with ddl-events. The main
pro of this approach is the ability to subscribe to (or unsubscribe
from) such events in run-time.
--
Angri
--~--~-~--~~~---~--~~
You received this message because you
extension...)
--
Angri
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to
sqlalchemy
it as an email attachment, or create a ticket in trac as
guest/guest and attach it there: http://www.sqlalchemy.org/trac/newticket
On Dec 10, 2008, at 5:19 PM, Angri wrote:
if you'd like to submit a patch which defines __visit_name__ for all
ClauseElements and removes the logic from
if you'd like to submit a patch which defines __visit_name__ for all
ClauseElements and removes the logic from VisitableType to guess the
name, it will be accepted. The second half of VisitableType still may
be needed since it improves performance.
Ok, I did it. Can not find where I
properties!)
instead of doing things like eval(Annotated%s %
element.__class__.__name__)?
On Dec 7, 1:33 am, Michael Bayer [EMAIL PROTECTED] wrote:
On Dec 6, 2008, at 4:27 PM, Angri wrote:
1. What about another side-effects depending on clsname? Is it
actually safe to extend
to extend sqlalchemy.schema.Column, or it may have
unpredictable behavior similar to that i've encountered?
2. (almost offtopic) Is 'exec' really need there? What's wrong with
closures?
3. Maybe I should send it to developers mailing list?
Thanks.
--
Angri
