Message147258
My initial instinct was to agree - the status code is useful. However, in looking at the FTP code, it sometimes just sets other objects (socket.error for example) as the 'reason'. The docs say 'reason' is a string or another exception.
I'm tempted to leave it as is. This fix is mainly to provide a reasonable value for .reason. The __str__ and .code are already exposed, so to create a reason with a code would create yet another string representation of the error which is different from every other representation already present. |
|
Date |
User |
Action |
Args |
2011-11-07 21:38:14 | jaraco | set | recipients:
+ jaraco, orsenthil, docs@python, petri.lehtinen |
2011-11-07 21:38:14 | jaraco | set | messageid: <1320701894.15.0.154419635988.issue13211@psf.upfronthosting.co.za> |
2011-11-07 21:38:13 | jaraco | link | issue13211 messages |
2011-11-07 21:38:13 | jaraco | create | |
|