[issue10589] I/O ABC docs should specify which methods have implementations

Andrew Svetlov added the comment: Fixed in a58204570a7c, 3cb85250a0a3, 93742b046519. -- assignee: stutzbach -> asvetlov resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker

[issue10589] I/O ABC docs should specify which methods have implementations

Andrew Svetlov added the comment: Updated the patch. Is it ok now? -- nosy: +asvetlov Added file: http://bugs.python.org/file28166/issue10589.diff ___ Python tracker ___

[issue10589] I/O ABC docs should specify which methods have implementations

Changes by Ezio Melotti : -- stage: needs patch -> patch review versions: +Python 3.3, Python 3.4 ___ Python tracker ___ ___ Python-bu

[issue10589] I/O ABC docs should specify which methods have implementations

Changes by Daniel Urban : -- nosy: +durban ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue10589] I/O ABC docs should specify which methods have implementations

Antoine Pitrou added the comment: > Other suggestions for a better name for that column are certainly welcome. :-) > > "Stub Methods"? Fine with me. -- ___ Python tracker ___

[issue10589] I/O ABC docs should specify which methods have implementations

Daniel Stutzbach added the comment: Other suggestions for a better name for that column are certainly welcome. :-) "Stub Methods"? -- ___ Python tracker ___ ___

[issue10589] I/O ABC docs should specify which methods have implementations

Antoine Pitrou added the comment: > > What does "unsupported" mean? "Abstract" would look more exact. > > It means they raise io.UnsupportedOperation when called (unless the > subclass overrides them to do something else). > > They are not marked with @abstractmethod, so "Abstract" would be

[issue10589] I/O ABC docs should specify which methods have implementations

Daniel Stutzbach added the comment: > What does "unsupported" mean? "Abstract" would look more exact. It means they raise io.UnsupportedOperation when called (unless the subclass overrides them to do something else). They are not marked with @abstractmethod, so "Abstract" would be wrong. I

[issue10589] I/O ABC docs should specify which methods have implementations

Georg Brandl added the comment: Not sure what "unsupported methods" means. E.g. "readinto" is listed as provided by RawIOBase in the doc text. -- ___ Python tracker ___ __

[issue10589] I/O ABC docs should specify which methods have implementations

Antoine Pitrou added the comment: What does "unsupported" mean? "Abstract" would look more exact. -- ___ Python tracker ___ ___ Pytho

[issue10589] I/O ABC docs should specify which methods have implementations

Changes by Fred L. Drake, Jr. : -- nosy: +d...@python, fdrake ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue10589] I/O ABC docs should specify which methods have implementations

Daniel Stutzbach added the comment: +io and doc people Attached is a simple patch to add a table to the documentation summarizing the I/O ABCs. -- keywords: +patch nosy: +benjamin.peterson, ezio.melotti, georg.brandl Added file: http://bugs.python.org/file19885/io-abc.diff __

[issue10589] I/O ABC docs should specify which methods have implementations

Changes by Antoine Pitrou : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue10589] I/O ABC docs should specify which methods have implementations

New submission from Daniel Stutzbach : The I/O ABC documentation has a blanket disclaimer at the top: "The abstract base classes also provide default implementations of some methods in order to help implementation of concrete stream classes. For example, BufferedIOBase provides unoptimized