This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author benjamin.peterson
Recipients amcnabb, benjamin.peterson
Date 2010-02-18.01:27:12
SpamBayes Score 4.088163e-11
Marked as misclassified No
Message-id <1afaf6161002171727o4a423208l1876b9d18a693e4f@mail.gmail.com>
In-reply-to <1266456167.71.0.672349998034.issue7954@psf.upfronthosting.co.za>
Content
2010/2/17 Andrew McNabb <report@bugs.python.org>:
>
> Andrew McNabb <amcnabb@mcnabbs.org> added the comment:
>
> Oops.  I had run "pydoc" instead of "pydoc3", so I was getting the 2.6 version of the io docstrings instead of the 3.1 version.
>
> By the way, it took about an hour to find out how to get Python 3 to treat stdin as bytes instead of unicode.  Now that I know what I was looking for, the documentation for the io library seems fine.  However, since Python 3 uptake is still a little slow, it's really hard to search for good information out there.

There's a note here: http://docs.python.org/py3k/library/sys#sys.stdin

>
> Would it be possible to some tutorial-style information to the io library documentation?  Stuff like switching stdin and stdout to bytes mode seem like they will be common problems, and it's a bit overwhelming to sort through 14 pages of documentation.  I think for most readers, it would be helpful to start with a brief tutorial before lunging into the hierarchy of abstract classes.
>
> Overall, the documentation is great; it's detailed and complete.  If there's one weakness, it's the overview.

Yes, but that's another issue. :)
History
Date User Action Args
2010-02-18 01:27:14benjamin.petersonsetrecipients: + benjamin.peterson, amcnabb
2010-02-18 01:27:12benjamin.petersonlinkissue7954 messages
2010-02-18 01:27:12benjamin.petersoncreate