On Sat, Oct 15, 2011 at 4:42 AM, Paul Moore p.f.mo...@gmail.com wrote:
I wish I felt more comfortable with MSI as a format (as opposed to an
opaque clickable installer). I'd be interested to know what others
think.
Compilation can be a problem on Linux systems as well, so a platform
neutral
On 15 October 2011 09:04, Nick Coghlan ncogh...@gmail.com wrote:
On Sat, Oct 15, 2011 at 4:42 AM, Paul Moore p.f.mo...@gmail.com wrote:
I wish I felt more comfortable with MSI as a format (as opposed to an
opaque clickable installer). I'd be interested to know what others
think.
Compilation
PyObject *tmp;
Py_identifier(update);
As I understand it, the macro expands to both the ID variable
declaration and the init-at-first-call code, right?
No. The variable will only get static initialization with the
char*. The initialization on first call (of the PyObject*) happens
in the
-- Issue #10517: After fork(), reinitialize the TLS used by the
PyGILState_* - APIs, to avoid a crash with the pthread implementation in
RHEL 5. Patch - by Charles-François Natali.
You should restore this NEWS entry and add a new one to say that the patch has
been reverted.
This may be a
On 10/15/2011 7:47 AM, Martin v. Löwis wrote:
-- Issue #10517: After fork(), reinitialize the TLS used by the
PyGILState_* - APIs, to avoid a crash with the pthread implementation in
RHEL 5. Patch - by Charles-François Natali.
You should restore this NEWS entry and add a new one to say that
On 10/7/2011 7:13 PM, Terry Reedy wrote:
On 10/7/2011 10:06 AM, Nick Coghlan wrote:
FWIW, I don't mind whether it's 0 or == -1, so long as there's a
comparison there to kick my brain out of Python boolean logic mode.
Is there any speed difference (on common x86/64 processors and
