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 hct
Recipients anon, hct, mark.dickinson, meador.inge, pitrou, rhettinger, serhiy.storchaka, tim.peters, vstinner
Date 2013-12-09.22:27:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> 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).

not sure what's semantically "seems wrong" with it. not sure why TypeError or any other error catching should come into play for this.

calling a function is way more expensive than doing bit shift and/or AND operation. as a function, you've only hide your code into Python binaries at the expense of performance
Date User Action Args
2013-12-09 22:27:55hctsetrecipients: + hct, tim.peters, rhettinger, mark.dickinson, pitrou, vstinner, meador.inge, serhiy.storchaka, anon
2013-12-09 22:27:55hctsetmessageid: <>
2013-12-09 22:27:55hctlinkissue19915 messages
2013-12-09 22:27:55hctcreate