Daniel Wagner-Hall added the comment: That is indeed the behaviour I'm talking about.
In particular I came across this where two libraries imported an exception type using different sys.path traversals, which both led to the same file, and a try-catch didn't catch the exception because it had a different type (even though it had been defined by the same file). This was a pretty horrible bug to track down. That said, messing with sys.path is pretty ugly, so I can see why this would be intentional, but it still feels like the the types of the same class, defined by the same file, should be equal. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15864> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
