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 christian.heimes
Recipients christian.heimes, neologix, serhiy.storchaka
Date 2013-07-01.21:36:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1372714589.72.0.868481547605.issue18328@psf.upfronthosting.co.za>
In-reply-to
Content
I was talking about memory address reuse, too. After all the code doesn't access data at the pointer's address but rather uses the address as an identifier.

I agree that the code should not behave erroneous under current circumstances. The GIL ensures serialization and provides a memory barrier. But it's hard to tell what might happen in the future and in embedded applications.

It smells fishy. :)
History
Date User Action Args
2013-07-01 21:36:29christian.heimessetrecipients: + christian.heimes, neologix, serhiy.storchaka
2013-07-01 21:36:29christian.heimessetmessageid: <1372714589.72.0.868481547605.issue18328@psf.upfronthosting.co.za>
2013-07-01 21:36:29christian.heimeslinkissue18328 messages
2013-07-01 21:36:29christian.heimescreate