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 teamnoir
Recipients adam.woodbeck, docs@python, eric.araujo, pitrou, teamnoir
Date 2011-06-07.17:07:29
SpamBayes Score 0.00034402625
Marked as misclassified No
Message-id <1307466450.81.0.616603024277.issue11203@psf.upfronthosting.co.za>
In-reply-to
Content
My point was for python-2.7.  I haven't stumbled into the buffer protocol yet.  So no, it doesn't really.

I still think the documentation, especially the 2.7 doc, could be more explicit.

My concern here is with the use of close() becoming obscure, a second class citizen, or an afterthought.  While I greatly appreciate the context manager, there are times when I want an enduring open channel for which the context manager just isn't appropriate.  Even in a world with context manager, open and close need to be available and presented as a pair.

It isn't clear to me from reading the doc or looking at the examples that gzip is expected to support a close call.  Yes, I concur that there is an implication, but I would prefer to see it stated explicitly along with the explicit statement that it supports an open call.
History
Date User Action Args
2011-06-07 17:07:30teamnoirsetrecipients: + teamnoir, pitrou, eric.araujo, docs@python, adam.woodbeck
2011-06-07 17:07:30teamnoirsetmessageid: <1307466450.81.0.616603024277.issue11203@psf.upfronthosting.co.za>
2011-06-07 17:07:30teamnoirlinkissue11203 messages
2011-06-07 17:07:29teamnoircreate