Nick Coghlan added the comment: Yes, this was a deliberate change to "flip the default" as to which subclasses get bad docstring behaviour.
In the status quo, if you provide a subclass method which does basically the same thing as the parent class, you lose the docstring unless you duplicate it, meaning you have to choose between bad docstrings and a maintainability problem due to content duplication. With this change, you only need a custom docstring in the subclass if you've changed the method behaviour enough that the parent class docstring no longer makes any sense. If you just want to suppress the docstring entirely, then you'll need to specify an empty docstring. This is potentially worth a note in the "Porting to Python 3.5" section of the What's New document, but it's an intended consequence of the change. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15582> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
