Type name varies in the repr() depending on the presence of the C extension about persistent HOT 3 CLOSED

Is there any reason not to fix the instance reprs to avoid this issue?

from persistent.

Is there any reason not to fix the instance reprs to avoid this issue?

I'm not quite sure what you mean. If you're asking, "can we make a change to cPersistence.Persistent to report the qualified name", my only answer is "it can be complicated" as discussed in the python-dev thread. Right now it's doing the simplest possible thing (largely because I don't consider myself a C API expert so I kept it simple). If you're asking "can we make a change to persistentce.Persistent to use the simple name", sure, we could, but we lose the module name, which is often useful. (That's a change I could implement.)

I'm not sure how big an issue this really is. BTrees was simple to fix. Still, it's an observable difference.

from persistent.

IDK :) Perhaps we expose the logical module name (e.g. BTrees.IOBTree.BTree) rather than the actual one.

IDK how big an issue it is either.

from persistent.