Author beazley
Recipients beazley, georg.brandl
Date 2008-12-27.13:14:38
SpamBayes Score 8.84538e-07
Marked as misclassified No
Message-id <1230383680.06.0.695552325819.issue4758@psf.upfronthosting.co.za>
In-reply-to
Content
I have recently completed a pretty thorough survey of library 
documentation for Python 3.0 in conjunction with an update I'm making to 
my book.   This issue is not so much a bug as a documentation request.

For all of the library modules related to network programming, it would 
be extremely useful to be much very explicit about what methods work 
with strings and what methods requires byte.  So many of these modules 
operate on small fragments of data (e.g., send a request, add a header, 
parse a query string, etc.).  Sometimes using a string is okay, 
sometimes it's not and sadly, it's not often predictable.   Part of the 
problem is that the documentation has been written for a Python 2 world 
where text strings and binary data were interchangeable.

Anyways, this request minimally covers these modules:
 
      ftplib
      smtplib
      nntplib
      http.*
      urllib.*
      xmlrpc.*
      socketserver
      asynchat
      asyncore
    
If there is interest, I can submit more detailed notes from my own work, 
but I'm not sure how the documentation maintainer would want this.  
Separate issue for each?   Added as comments here?   Please advise.
History
Date User Action Args
2008-12-27 13:14:40beazleysetrecipients: + beazley, georg.brandl
2008-12-27 13:14:40beazleysetmessageid: <1230383680.06.0.695552325819.issue4758@psf.upfronthosting.co.za>
2008-12-27 13:14:39beazleylinkissue4758 messages
2008-12-27 13:14:38beazleycreate