Message107083
| Author |
jmfauth |
| Recipients |
docs@python, eric.araujo, jmfauth, r.david.murray |
| Date |
2010年06月04日.17:45:52 |
| SpamBayes Score |
0.0031967233 |
| Marked as misclassified |
No |
| Message-id |
<AANLkTimsgmkbzdOEfpJ0DDDk_G8IKxYmLERZXDBZAf6V@mail.gmail.com> |
| In-reply-to |
<1275659351.45.0.959470544624.issue8895@psf.upfronthosting.co.za> |
| Content |
2010年6月4日 Éric Araujo <report@bugs.python.org>
>
> Éric Araujo <merwok@netwok.org> added the comment:
>
> Could you think of a way to improve the docs on that point?
>
> ----------
>
> Quick and dirty answer.
I have ~10 years experience with Python and it seems
to me the io module is technically excellent.
However, I have found it is not so obvious to
understand the usage of all these arguments,
errors, encoding, line_buffering, ... in the
class constructors and methods like io.open().
The doc describes what these arguments are,
their states, but not too much how to use
them.
As an exemple, I read some time ago on the c.l.p
mailing list, somebody complaining about the "encoding"
argument of the class TextIOWrapper. He defined an
"encoding='utf-8'" in the ctor and did not
understand why his "text" was not automagically
encoded. Answer: the encoding arg is only a kind
of information and does not do anything.
BTW, it was only when I read that post, I understand
a little bit more.
Regards. |
| Files |
| File name |
Uploaded |
|
unnamed
|
jmfauth,
2010年06月04日.17:45:52
|
|