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 erik.bray
Recipients EdSchouten, erik.bray, r.david.murray, vstinner
Date 2016-08-23.15:05:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1471964756.73.0.654930622453.issue25658@psf.upfronthosting.co.za>
In-reply-to
Content
The good news about this (in the pthread case) is that it does not need to be seen as some workaround for unusual platforms, but rather making the existing code more POSIX-compliant (and hence correct).

The Win32 side I'm a little less worried about because the TLS key is documented to be a DWORD, and so the existing casting to int should still work fine most of the time.  However, the docs for TlsAlloc() (https://msdn.microsoft.com/en-us/library/windows/desktop/ms686801(v=vs.85).aspx) do state:

> The value of the TLS index should be treated as an opaque value; do not assume that it is an index into a zero-based array.

which again makes #22206 suspect :(
History
Date User Action Args
2016-08-23 15:05:56erik.braysetrecipients: + erik.bray, vstinner, r.david.murray, EdSchouten
2016-08-23 15:05:56erik.braysetmessageid: <1471964756.73.0.654930622453.issue25658@psf.upfronthosting.co.za>
2016-08-23 15:05:56erik.braylinkissue25658 messages
2016-08-23 15:05:56erik.braycreate