avoiding autoregistry.exceptions.KeyCollisionError

[jsiverskog]

hi,
we're using importlib.util.module_from_spec to find classes in a number of files. one of these files contain a Device subclass. when that file is parsed the second time (since it's imported subclassed from another file) belay causes this crash:

autoregistry.exceptions.KeyCollisionError: "iohubwithusbflipper" already registered to {'iohub': <IoHub: ['iohubv3', 'iohubv2', 'iohubv1', 'iohubwithusbflipper']>, 'iohubv3': <IoHubV3: ['iohubwithusbflipper']>, 'iohubv2': <IoHubV2: []>, 'iohubv1': <IoHubV1: []>, 'stacklight': <Stacklight: []>, 'iohubwithusbflipper': <IoHubWithUsbFlipper: []>}

i saw that autoregistry supports an overwrite argument to avoid this error, but is there any way i can set the overwrite argument to True through belay?

thanks, jacob

[jsiverskog]

actually, if moving the class to a separate file it works.

it did not work with this structure:

file_a.py [defines Device subclass, and defines ClassA]
file_b.py [imports file_a, defines ClassB as subclass of ClassA]

but works with this:

device_sub.py [defines Device subclass]
file_a.py [defines ClassA]
file_b.py [imports file_a, defines ClassB as subclass of ClassA]

when i run importlib.util.spec_from_file_location and then importlib.util.module_from_spec on file_a.py and then file_b.py.

[BrianPugh]

hmmm, I wonder if I can solve this by detecting these redundant definitions within autoregistry and have it not trigger a KeyCollisionError, this is a bit of an interesting edge case. Hopefully I should be able to investigate within the next few days.