Message219995
I have verified that this feature is unused in the source tree; in fact, there are no internal calls to bytearray_getbuffer() at all. The only thing bytearray_getbuffer() does with its second arg is pass it to PyBuffer_FillInfo(), which immediately checks it and passes 0 up the call stack if it is NULL. (A comment in PyBuffer_FillInfo() asks why -1 is not passed up instead; it's probably to distinguish this feature from the error condition handled in the immediately following conditional block.)
There are potentially other issues stemming from this legacy feature in bytearray_getbuffer(), PyBuffer_FillInfo(), and elsewhere. The maintainers may see fit to open tickets on these issues as well.
There's more relevant commentary on the feature here: http://comments.gmane.org/gmane.comp.python.devel/130521 |
|
Date |
User |
Action |
Args |
2014-06-07 22:51:54 | kelleynnn | set | recipients:
+ kelleynnn, ncoghlan, pitrou, skrah |
2014-06-07 22:51:54 | kelleynnn | set | messageid: <1402181514.13.0.231550585076.issue14203@psf.upfronthosting.co.za> |
2014-06-07 22:51:54 | kelleynnn | link | issue14203 messages |
2014-06-07 22:51:53 | kelleynnn | create | |
|