Thomas Heller (Guido, Thomas, Guido): > [Guido] > > > > I guess I still don't understand Neil's requirements. What can't be > > > > done with the existing buffer interface (which requires you to hold > > > > the GIL while using the pointer)? > > > > > > Processing in Python :-(. > > > > Can you work out an example? > Not sure, maybe Neil could do it better. I see this interface as a bridge between objects offering generic buffer oriented facilities (asynch or low level I/O for example) and objects that want to make it possible to use these facilities on their data (text buffers, multimedia buffers, numeric arrays) by yielding a pointer to their otherwise internal data. The bridging code between the two objects is unrestricted Python code that may cause memory to be moved around. 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