ComplexModels attempting to use in-line customization are silently dropped from inheriting objects about spyne HOT 2 CLOSED

hey,

i may be stuck at home but it's still a nice friday evening, so just a quick response:

SomeComplexModel(foo=bla, bar=bla, ...) instantiates said model. no way around that as that's how python classes work.
Integer64(min_occurs=1) customizes said model. if you want to instantiate, use int() or Integer64.Value() if you want to be consistent.

class Obj2(ComplexModel):
    # Obj1 gets siletly dropped from obj2 when instantiating obj2
    A = Obj1(min_occurs = 0, max_occurs = 1)

the code here sets a class variable A. ComplexModelMeta ignores it as it's a legitimate python instantiation and not a ModelBase type. you need Obj1.customize() if you want to establish a has-a relationship between Obj2 and Obj1.

If this doesn't help that's probably because i only skimmed your question and i'll look at this more closely when it's work time, so bear with me

best,

from spyne.

I'm reading that as There are reasons under the covers complexModels can't have the same short cut as simple models, and I'm going to take a swing at a doc update to make this more clear to a new dev. Since this is an expected behavior, I'm going to close this issue, and reference it in the PR.

from spyne.