➜

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 anon
Recipients anon, hct, mark.dickinson, rhettinger, serhiy.storchaka, tim.peters
Date 2013-12-07.11:19:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1386415169.35.0.798178286397.issue19915@psf.upfronthosting.co.za>
In-reply-to
Content 
I like the i.bits_at(pos, width=1) suggestion. Unless slicing is chosen instead this seems the most future-proof idea.

I think slicing semantically "seems wrong" but it might be more elegant. It might also make catching errors harder (in the case where an int is sent to a function that does slicing and now won't fail with a TypeError).
History
Date User Action Args
2013-12-07 11:19:29anonsetrecipients: + anon, tim.peters, rhettinger, mark.dickinson, serhiy.storchaka, hct
2013-12-07 11:19:29anonsetmessageid: <1386415169.35.0.798178286397.issue19915@psf.upfronthosting.co.za>
2013-12-07 11:19:29anonlinkissue19915 messages
2013-12-07 11:19:29anoncreate