[Tim]
> I'm trying to cater to allocating via PyMem_{MALLOC, Malloc} then
> free'ing via _PyMalloc_Free.
[Martin]
> Is *that* the motivation?
One of them.
> I thought you were trying to accommodate your killer.py where Python
> code can trick pymalloc into believing that it owned the memory which
> it actually had allocated by forwarding to system malloc
That's another one. There are only two, so we can stop now <wink>.
> (see the subject).
That came from the first msg in the thread. The second msg in the thread
came a couple days later, and broadened the scope at its start:
http://mail.python.org/pipermail/python-dev/2002-March/021905.html
It was too easy to *just* fix killer.py <wink>.
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