Author ncoghlan
Recipients benjamin.peterson, docs@python, eric.araujo, ezio.melotti, georg.brandl, hynek, ncoghlan, nikratio, pitrou, r.david.murray, rhettinger, stutzbach
Date 2014-06-17.21:52:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7eNNYNsv387rZ9twOkS1ciSne6cXUVUmXSFm5yZA7v0sQ@mail.gmail.com>
In-reply-to <1403038745.76.0.418771035787.issue21763@psf.upfronthosting.co.za>
Content
I can add a third suggestion: a "HOWTO" guide on implementing and using
file-like objects. It's actually a somewhat complex topic with various
trade-offs involved, particularly in Python 3 where the differences between
binary and text IO are greater. It could also point users to existing
file-like objects that they may have missed (like the spooled temporary
file support in tempfile).

On the more specific matter at hand, I think "close() is idempotent" is not
only one of our most pervasive assumptions about file-like objects, but
also an assumption we tend to make about resources *in general*.
History
Date User Action Args
2014-06-17 21:52:47ncoghlansetrecipients: + ncoghlan, georg.brandl, rhettinger, pitrou, benjamin.peterson, stutzbach, ezio.melotti, eric.araujo, r.david.murray, nikratio, docs@python, hynek
2014-06-17 21:52:47ncoghlanlinkissue21763 messages
2014-06-17 21:52:47ncoghlancreate