➜

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 mark.dickinson
Recipients mark.dickinson, serhiy.storchaka
Date 2012-10-18.12:56:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1350564991.53.0.447049972916.issue16277@psf.upfronthosting.co.za>
In-reply-to
Content 
First part of the patch looks fine to me.

For the second part, I don't see any undefined behaviour here.  Can you explain where the undefined behaviour comes from?  And are you sure that this is really just an optimization?  It looks as though it might be deliberately there to make sure that the conversion still produces a Python 0 even on systems where the NULL pointer *doesn't* give 0 when converted to an integer.
History
Date User Action Args
2012-10-18 12:56:31mark.dickinsonsetrecipients: + mark.dickinson, serhiy.storchaka
2012-10-18 12:56:31mark.dickinsonsetmessageid: <1350564991.53.0.447049972916.issue16277@psf.upfronthosting.co.za>
2012-10-18 12:56:31mark.dickinsonlinkissue16277 messages
2012-10-18 12:56:31mark.dickinsoncreate