➜

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 anon, georg.brandl, hct, josh.r, mark.dickinson, martin.panter, meador.inge, pitrou, rhettinger, serhiy.storchaka, tim.peters, vstinner
Date 2014-10-02.11:48:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1412250528.78.0.147644716601.issue19915@psf.upfronthosting.co.za>
In-reply-to
Content 
> - no need to depreciate x.bit_length

No matter how this issue progresses, deprecating `int.bit_length` should be out of the question.  Much better to have (somewhat) duplicated functionality than to gratuitously break code that's already using `int.bit_length`.
History
Date User Action Args
2014-10-02 11:48:48mark.dickinsonsetrecipients: + mark.dickinson, tim.peters, georg.brandl, rhettinger, pitrou, vstinner, meador.inge, martin.panter, serhiy.storchaka, hct, anon, josh.r
2014-10-02 11:48:48mark.dickinsonsetmessageid: <1412250528.78.0.147644716601.issue19915@psf.upfronthosting.co.za>
2014-10-02 11:48:48mark.dickinsonlinkissue19915 messages
2014-10-02 11:48:48mark.dickinsoncreate