This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author takluyver
Recipients Dhiraj_Mishra, martin.panter, mbussonn, python-dev, serhiy.storchaka, takluyver
Date 2016-05-14.21:25:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
1. For the cases like read/write handles conflicting, ValueError doesn't seem quite right to me - I take ValueError to mean that you have passed an invalid value to a function. RuntimeError feels like the closest fit for 'the current state does not allow this operation'. It is rather broad, though.

If I was writing it anew, I would use ValueError for something like an invalid mode parameter:'foo', mode='q') . That particular case was already in the code, though, so I think backwards compatibility should take precedence.

2 & 3. Agreed, I'll prepare a patch
Date User Action Args
2016-05-14 21:25:05takluyversetrecipients: + takluyver, python-dev, martin.panter, serhiy.storchaka, mbussonn, Dhiraj_Mishra
2016-05-14 21:25:05takluyversetmessageid: <>
2016-05-14 21:25:05takluyverlinkissue26039 messages
2016-05-14 21:25:05takluyvercreate