Author cbay
Recipients cbay, giampaolo.rodola, janssen, pitrou, r.david.murray, vstinner
Date 2010-03-26.18:47:39
SpamBayes Score 2.27149e-05
Marked as misclassified No
Message-id <1269629261.09.0.26318395745.issue8240@psf.upfronthosting.co.za>
In-reply-to
Content
pitrou: that's debatable, since the Python programmer has no control over memory pointers. As I said, I have a cStringIO buffer, and two consecutive calls to buffer.getvalue() yield different objects. What can I do about it? I think it's a rather sane scenario, and I don't feel I'm doing anything wrong.

If you think the programmer should be alerted about it, however, then we should at least say it explicitely in the documentation and probably return an explicit Python error. I had to google quite a bit before finding out what this error meant:

error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry
History
Date User Action Args
2010-03-26 18:47:41cbaysetrecipients: + cbay, janssen, pitrou, vstinner, giampaolo.rodola, r.david.murray
2010-03-26 18:47:41cbaysetmessageid: <1269629261.09.0.26318395745.issue8240@psf.upfronthosting.co.za>
2010-03-26 18:47:39cbaylinkissue8240 messages
2010-03-26 18:47:39cbaycreate