Neal Norwitz nnorwitz at gmail.com
Mon Sep 19 18:55:36 CEST 2005

• Previous message: [Python-Dev] possible memory leak on windows (valgrind report)
• Next message: [Python-Dev] possible memory leak on windows (valgrind report)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On 9/19/05, Guido van Rossum <guido at python.org> wrote:
> 
> That patch doesn't make sense to me -- the "s" code to
> PyArg_ParseTuple doesn't return newly allocated memory, it just
> returns a pointer into a string object that is owned by the caller
> (really by the call machinery I suppose). Compare other places using
> PyArg_ParseTuple(args, "s:...").

"s"?  The format passed to ParseTuple is "et".  At least it is in the
patch I'm looking at.

n

---

• Previous message: [Python-Dev] possible memory leak on windows (valgrind report)
• Next message: [Python-Dev] possible memory leak on windows (valgrind report)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list