> but I'm sure there is a way that `MYTYPE = object()` will come back to absolutely ruin your day if you have to compare two `MYTYPE` instances in two different dicts derived from a parent process and a subprocess.
I don't see how this can be an issue with imports. You have two cases: you imported the module with MTYPE before or after fork. Before: they will compare fine. (unless IPC's involved) After: you transferred the dict with MTYPE through some kind of serialisation or shmem and you cannot compare identities - that's a property of IPC rather than something to do with python modules.
Anyway, what I meant in previous comment was the risk matrix view. Sure, this can lead to bugs scoring various points in severity, but does it score high on likelihood?
I don't see how this can be an issue with imports. You have two cases: you imported the module with MTYPE before or after fork. Before: they will compare fine. (unless IPC's involved) After: you transferred the dict with MTYPE through some kind of serialisation or shmem and you cannot compare identities - that's a property of IPC rather than something to do with python modules.
Anyway, what I meant in previous comment was the risk matrix view. Sure, this can lead to bugs scoring various points in severity, but does it score high on likelihood?