➜

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 serhiy.storchaka
Recipients loewis, martin.panter, ned.deily, rhettinger, serhiy.storchaka, vstinner, xiang.zhang
Date 2016-04-22.09:06:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1461316012.33.0.0163161147652.issue26824@psf.upfronthosting.co.za>
In-reply-to
Content 
How this can help reduce the possible errors? I afraid that it rather can increase the possibility of error.

There is no undefined behaviour in current code. It was in old code (in the casting a pointer to PyObject*), but this was fixed with new PyObject_HEAD in 3.0+. 2.7 still has this undefined behaviour.
History
Date User Action Args
2016-04-22 09:06:52serhiy.storchakasetrecipients: + serhiy.storchaka, loewis, rhettinger, vstinner, ned.deily, martin.panter, xiang.zhang
2016-04-22 09:06:52serhiy.storchakasetmessageid: <1461316012.33.0.0163161147652.issue26824@psf.upfronthosting.co.za>
2016-04-22 09:06:52serhiy.storchakalinkissue26824 messages
2016-04-22 09:06:52serhiy.storchakacreate