[issue15034] Devguide should document best practices for stdlib exceptions

Changes by Chris Jerdonek : -- nosy: +cjerdonek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue15034] Devguide should document best practices for stdlib exceptions

Terry J. Reedy added the comment: I think the Library Manual's chapter 5 on exceptions, currently called Built-in Exceptions, would be a good place for a section on subclassing exceptions. -- ___ Python tracker __

[issue15034] Devguide should document best practices for stdlib exceptions

Ezio Melotti added the comment: I'm not sure this belongs to the devguide. Ideally the best way to do it should be documented in the docs. This doesn't necessary mean it should be in the tutorial, but if the way documented in the tutorial is "wrong", I'd rather tell users "this is the right way

[issue15034] Devguide should document best practices for stdlib exceptions

Terry J. Reedy added the comment: I agree with Raymond that this, especially super() is not tutorial material. I agree with David that we need something somewhere else. Just today a commit was pushed about IOException subclasses causing problems because they have an __init__ but don't call su

[issue15034] Devguide should document best practices for stdlib exceptions

Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue15034] Devguide should document best practices for stdlib exceptions

R. David Murray added the comment: OK, let's move this, then. I asked the question because I'd like to know what the best practice is for exceptions in the stdlib. This is an area in which we have made quite a bit of progress recently (ie: the work done on exceptions for Python3, and PEP 31