Message11345
I have a pull request to fix this one https://github.com/jythontools/jython/pull/75
The patch I have submitted uses the same work around already present for another exception type. It seems like a better solution would be to look in the exception map for the type, then if not found it's super-type and so on. Then only fall through if there are no mapped exceptions, in the actual exceptions type hierarchy. If this approach would be preferred I don't mind having a better look at this one. With this fixed I now have no test failures on linux. |
|
Date |
User |
Action |
Args |
2017-05-04 18:35:47 | jamesmudd | set | messageid: <1493922947.28.0.486684594116.issue2585@psf.upfronthosting.co.za> |
2017-05-04 18:35:47 | jamesmudd | set | recipients:
+ jamesmudd |
2017-05-04 18:35:47 | jamesmudd | link | issue2585 messages |
2017-05-04 18:35:46 | jamesmudd | create | |
|