[Python-Dev] doc for new restricted execution design for Python
Brett Cannon
brett at python.org
Thu Jun 22 15:46:29 CEST 2006
More information about the Python-Dev mailing list
Thu Jun 22 15:46:29 CEST 2006
- Previous message: [Python-Dev] doc for new restricted execution design for Python
- Next message: [Python-Dev] doc for new restricted execution design for Python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 6/22/06, Gerhard Häring <gh at ghaering.de> wrote: > > Brett Cannon wrote: > > I have been working on a design doc for restricted execution of Python > > [...] > > All the rest of the API made sense to me, but I couldn't understand why > > PyXXX_MemoryFree > > is needed. How could memory usage possibly fall below 0? It can't in real life, but people could call MemoryFree() too many times. Plus you need some way to lower the amount when memory is freed. No need to penalize a script that does a bunch of malloc/free calls compared to one that just does a bunch of malloc calls. -Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20060622/c0efc91b/attachment.htm
- Previous message: [Python-Dev] doc for new restricted execution design for Python
- Next message: [Python-Dev] doc for new restricted execution design for Python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list