Thomas Heller <theller at python.net> wrote: > AFAIK, the buffer object now does not hold a pointer into the object > it has been constructed from, it only gets it when its needed. > > IMO Objects/bufferobject.c, revision 35400 is considered safe. > > The checkin comment (by nascheme) was, more than 2 years ago: > "Make buffer objects based on mutable objects (like array) safe." It's good to hear that bug has been squished. I believe buffer() is generally safe then, according to my somewhat limited experience in its use and knowledge about its implementation. - Josiah
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