Oct. 29, 2003
11:56 p.m.
On Thu, Oct 30, 2003 at 10:21:50AM +1100, Mark Hammond wrote:
As the essence of the solution, I think that sounds good!
Thanks for the feedback. It seems you are one of the few who are familiar with this interrface.
I think that the following should also be done:
* Update the docs for the buffer functions to indicate that these are *short term* pointers, that are not guaranteed once *any* Python code is called.
* Add new public buffer functions with "LongTerm" in the name (and docs that buffer is valid as long as the object). These check the flag as you propose.
* Buffer object uses new LongTerm buffer functions.
Seems easy enough. I'll make a patch. Neil