[issue9613] Python considers pid longs under 64-bit Windows

2013-10-13 Thread Antoine Pitrou
Antoine Pitrou added the comment: Amaury is right, it seems a Windows pid is an int after all. I don't know where I got the other impression :-) -- resolution: -> invalid stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue9613] Python considers pid longs under 64-bit Windows

2013-10-13 Thread Georg Brandl
Georg Brandl added the comment: Antoine, ping? -- nosy: +georg.brandl status: pending -> open ___ Python tracker ___ ___ Python-bugs-li

[issue9613] Python considers pid longs under 64-bit Windows

2012-11-19 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- status: open -> pending ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue9613] Python considers pid longs under 64-bit Windows

2010-08-26 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: The spawn* functions return intptr_t, because it's the process handle. But _getpid() returns an int. Both seem to be correctly handled. Which part do you suspect to truncate data? -- nosy: +amaury.forgeotdarc

[issue9613] Python considers pid longs under 64-bit Windows

2010-08-15 Thread Antoine Pitrou
New submission from Antoine Pitrou : Under 64-bit Windows, Python aliases PyLong_FromPid() to PyLong_FromLong() (and PyLong_AsPid() to PyLong_AsLong()), but a C "long" is 32-bit, while apparently the MSVCRT defines a pid to be intptr_t, that is 64-bit. A potential loss of data ensues. ---