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
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4