This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients amaury.forgeotdarc, eric.smith, neologix, pitrou
Date 2011-03-03.11:25:08
SpamBayes Score 1.0334451e-08
Marked as misclassified No
Message-id <1299151510.35.0.785537757742.issue11382@psf.upfronthosting.co.za>
In-reply-to
Content
I didn't even know that Windows had such calls.
But anyway, if we start releasing the GIL around each malloc call, then it's going to get really complicated:

static PyObject *
posix_geteuid(PyObject *self, PyObject *noargs)
{
 	return PyLong_FromLong((long)geteuid());
}

PyLong_FromLong -> _PyLong_New -> PyObject_MALLOC which can call malloc.

As for DuplicateHandle, I assume it's as fast as Unix's dup(2).
History
Date User Action Args
2011-03-03 11:25:10neologixsetrecipients: + neologix, amaury.forgeotdarc, pitrou, eric.smith
2011-03-03 11:25:10neologixsetmessageid: <1299151510.35.0.785537757742.issue11382@psf.upfronthosting.co.za>
2011-03-03 11:25:08neologixlinkissue11382 messages
2011-03-03 11:25:08neologixcreate