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 Sergey.Litvinov, mark.dickinson, rhettinger, serhiy.storchaka
Date 2014-12-08.17:37:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1418060269.97.0.535649167419.issue23007@psf.upfronthosting.co.za>
In-reply-to
Content
> What troubles?

Well, I imagine that something like "bisect(a, 155, lo=numpy.uint8(0), hi=numpy.uint8(254))" would be asking for trouble.  But (a) it's hard to imagine why anyone would want to do that given that NumPy has its own bisection code, and (b) you'd have to somehow make sure that you were using the plain Python bisect code and not the `_bisect` module code, which AFAIK does the right thing here.

Sergey: what troubles have you run into?  With what user-defined types?  Note that if you just do "from bisect import *" at a Python prompt, you're not even using the code in Lib/bisect.py: the main implementation is written in C.
History
Date User Action Args
2014-12-08 17:37:50mark.dickinsonsetrecipients: + mark.dickinson, rhettinger, serhiy.storchaka, Sergey.Litvinov
2014-12-08 17:37:49mark.dickinsonsetmessageid: <1418060269.97.0.535649167419.issue23007@psf.upfronthosting.co.za>
2014-12-08 17:37:49mark.dickinsonlinkissue23007 messages
2014-12-08 17:37:49mark.dickinsoncreate