[issue15731] Mechanism for inheriting docstrings and signatures

Serhiy Storchaka added the comment: After issue15582, is it still actual? -- ___ Python tracker ___ ___

[issue15731] Mechanism for inheriting docstrings and signatures

Nick Coghlan added the comment: Agreed, making it easy to follow the inheritance chains at docstring lookup time means it would be redundant to duplicate them at class definition time. Code that interrogates __doc__ directly rather than using inspect.getdoc won't benefit from the new

[issue15731] Mechanism for inheriting docstrings and signatures

Changes by Yury Selivanov yselivanov...@gmail.com: -- nosy: +yselivanov versions: +Python 3.5 -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15731 ___

[issue15731] Mechanism for inheriting docstrings and signatures

Yury Selivanov added the comment: Perhaps, something like @functools.inherit decorator could help: https://gist.github.com/1st1/8703533 (just a quick illustration). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15731

[issue15731] Mechanism for inheriting docstrings and signatures

Changes by Serhiy Storchaka storch...@gmail.com: -- nosy: +serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15731 ___ ___

[issue15731] Mechanism for inheriting docstrings and signatures

Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15731 ___

[issue15731] Mechanism for inheriting docstrings and signatures

Changes by Chris Rebert pyb...@rebertia.com: -- nosy: +cvrebert ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15731 ___ ___ Python-bugs-list

[issue15731] Mechanism for inheriting docstrings and signatures

Ben Finney added the comment: Attached is a patch which is more comprehensive (covering the additional locations pointed out to me by ncoghlan), and also consolidating the details into the library documentation so they're not verbosely repeated in so many places. I agree with Nick's position

[issue15731] Mechanism for inheriting docstrings and signatures

Ben Finney added the comment: Apologies, my previous comment and patch was sent to the wrong issue (should have gone to #8810). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15731 ___

[issue15731] Mechanism for inheriting docstrings and signatures

Changes by Andrew Svetlov andrew.svet...@gmail.com: -- nosy: +asvetlov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15731 ___ ___

[issue15731] Mechanism for inheriting docstrings and signatures

Changes by Nick Coghlan ncogh...@gmail.com: -- Removed message: http://bugs.python.org/msg168621 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15731 ___

[issue15731] Mechanism for inheriting docstrings and signatures

Changes by Nick Coghlan ncogh...@gmail.com: -- Removed message: http://bugs.python.org/msg168622 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15731 ___

[issue15731] Mechanism for inheriting docstrings and signatures

Changes by Nick Coghlan ncogh...@gmail.com: Removed file: http://bugs.python.org/file26910/issue8810_reconcile_docs.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15731 ___

[issue15731] Mechanism for inheriting docstrings and signatures

New submission from Nick Coghlan: While working on #8810, I was reminded of the problem of wanting to inherit docstrings while replacing a method implementation. The abstract base class method docstrings for tzinfo.utcoffset and tzinfo.dst are also correct for the concrete subclasses in the

[issue15731] Mechanism for inheriting docstrings and signatures

Nick Coghlan added the comment: Slight correction: turns out this docstring appears in a lot of other places, too. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15731 ___