[sqlalchemy] association_proxy usage in non-declarative style

2012-01-11 Thread Phazorx
Hello, i am trying to figure out how association_proxy() could be used in case of regular rather than declarative style definitions. I can't figure out what can be done to mitigate the issue and hence i seek help here. Thanks in advance... The code below is copy/pasted sample from the official

[sqlalchemy] Re: keyword-only arguments in entity constructor confuse mapper

2011-08-08 Thread Phazorx
contract that the *, x, y syntax describes ?  or can you suddenly pass first_name, last_name positionally as well ? On Aug 5, 2011, at 2:20 AM, Phazorx wrote: The patch worked on 0.7.0 and i don't get warning from Python (3.2), so it seem to have addressed the issue correctly. (Well i

[sqlalchemy] Re: keyword-only arguments in entity constructor confuse mapper

2011-08-05 Thread Phazorx
...@zzzcomputing.com wrote: On Jul 29, 2011, at 3:45 AM, Phazorx wrote: Most of my entities accept various combinations of parameters and it makes sense for my to use keyword-only pattern of constructors: class Person(Root_Entity):    def __init__(self, session, *, first_name, last_name): class

[sqlalchemy] keyword-only arguments in entity constructor confuse mapper

2011-07-29 Thread Phazorx
Most of my entities accept various combinations of parameters and it makes sense for my to use keyword-only pattern of constructors: class Person(Root_Entity): def __init__(self, session, *, first_name, last_name): class Address(Root_Entity): def __init__(self, session, *, street,