Message169848
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. |
|
Date |
User |
Action |
Args |
2012-09-04 23:57:36 | daniel.wagner-hall | set | recipients:
+ daniel.wagner-hall, pitrou, r.david.murray |
2012-09-04 23:57:32 | daniel.wagner-hall | set | messageid: <1346803052.68.0.0938995143861.issue15864@psf.upfronthosting.co.za> |
2012-09-04 23:57:32 | daniel.wagner-hall | link | issue15864 messages |
2012-09-04 23:57:31 | daniel.wagner-hall | create | |
|