Tony

I have to say that I would like this too. Having the runspaces ready to go would improve performance so much at the cost of a longer one-time initial startup.

Hmmm, that seems interesting. I know python well enough but I'm a noob when it comes to KVM/QEMU. I'll try to look into the other issue.

Hi @smk4664, Thank you for the quick reply. I'm trying to figure out what you're describing here. I'll postfix everything with either A or B when discussing this. Suppose I...

Now I understand what you meant and it is actually what I'm doing right now. ```python class Attachment(DiffSyncModel): _modelname = "attachment" _identifiers = ("name",) _shortname = () _attributes = (...

Hi @Kircheneer, it would be a nice feature to have, but this workaround suffices. Thank you for the help :)

The configuration example is folded btw in the original post.

Same, would like for this feature as well!

Managed to get something working by creating a wrapper class: ```python class ValidxWrap(validx.cy.Validator): """ Wraps classes in ValidX """ step: validx.cy.Validator metadata: t.Optional[t.Dict] def __init__( self, step: validx.cy.Validator, metadata: t.Optional[t.Dict]...

In this case I'd like for the `Int()` validator on `x` to return that metadata. I'm not sure what to do if the dict and schema also has a key...

Ah, that is a good point. For us, we're mostly interested in the metadata for the place the error occurs. ```python schema = Dict( { "x": Int(metadata={"somevalue": 1}), "y": Str(metadata={"somevalue":...