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 pitrou
Recipients bdkearns, pitrou, stutzbach, tim.golden, zach.ware
Date 2014-04-26.11:32:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398511959.2296.2.camel@fsol>
In-reply-to <1398479050.42.0.656819371332.issue21349@psf.upfronthosting.co.za>
Content
> Are you aware of the old/new buffer interfaces and their usages? Did
> you actually try the code? "crash" would be obvious.

I cannot try the code as I'm under Linux :-)
I was asking merely because many people report plain exception
tracebacks as "crashes". Yes, by reading the patch it came to me that it
was probably related to the coexistence of old and new buffer API, but I
prefer it to be confirmed by the reporter, rather than trust my own
intuition.

(I also wonder why the code did that manually instead of calling e.g.
PyObject_AsReadBuffer)
History
Date User Action Args
2014-04-26 11:32:42pitrousetrecipients: + pitrou, tim.golden, stutzbach, zach.ware, bdkearns
2014-04-26 11:32:42pitroulinkissue21349 messages
2014-04-26 11:32:41pitroucreate