summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBenjamin Peterson <benjamin@python.org>2011-02-24 02:46:00 (GMT)
committerBenjamin Peterson <benjamin@python.org>2011-02-24 02:46:00 (GMT)
commit634ef9cb81ad66b335778422cd7e51bb483b9e3e (patch)
treed0f302fc8832b1044fe12b9d2c90d0495a955439
parenta6f85e22706f989340b1c29b7e3be04905bfb8ef (diff)
downloadcpython-634ef9cb81ad66b335778422cd7e51bb483b9e3e.zip
cpython-634ef9cb81ad66b335778422cd7e51bb483b9e3e.tar.gz
cpython-634ef9cb81ad66b335778422cd7e51bb483b9e3e.tar.bz2
this seems to be pointlessly nested
-rw-r--r--Doc/library/io.rst15
1 files changed, 6 insertions, 9 deletions
diff --git a/Doc/library/io.rst b/Doc/library/io.rst
index 26ddd8f..9828662 100644
--- a/Doc/library/io.rst
+++ b/Doc/library/io.rst
@@ -785,17 +785,14 @@ Text I/O
inherits :class:`codecs.IncrementalDecoder`.
-Advanced topics
----------------
-
-Here we will discuss several advanced topics pertaining to the concrete
-I/O implementations described above.
-
Performance
-^^^^^^^^^^^
+-----------
+
+This section discusses the performance of the provided concrete IO
+implementations.
Binary I/O
-""""""""""
+^^^^^^^^^^
By reading and writing only large chunks of data even when the user asks
for a single byte, buffered I/O is designed to hide any inefficiency in
@@ -808,7 +805,7 @@ platform and the backing device. Therefore, it is most always preferable to
use buffered I/O rather than unbuffered I/O.
Text I/O
-""""""""
+^^^^^^^^
Text I/O over a binary storage (such as a file) is significantly slower than
binary I/O over the same storage, because it implies conversions from