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 timehorse
Recipients loewis, niemeyer, timehorse, tlynn
Date 2008-10-13.13:31:12
SpamBayes Score 0.00016903925
Marked as misclassified No
Message-id <1223904673.94.0.159989260861.issue1708652@psf.upfronthosting.co.za>
In-reply-to
Content
Binary format searches should be supported once issue 1282 is implemented, 
likely as part of issue 2636 Item 32.  That said, I'm not clear what you 
mean by exact search; wouldn't you want match instead?  If your main issue 
is you want something that automatically binds to the beginning and ending 
of input, then I suppose we could add an 'exact' method where 'search' 
searches anywhere, 'match' matches from the start of input and 'exact' 
matches from beginning to ending.  I'd call that a separate issue, though.  
In other words: byte-oriented matches is covered by 1282 and adding an 
'exact' method is the only new issue here.  Does that sound right?
History
Date User Action Args
2008-10-13 13:31:14timehorsesetrecipients: + timehorse, loewis, niemeyer, tlynn
2008-10-13 13:31:13timehorsesetmessageid: <1223904673.94.0.159989260861.issue1708652@psf.upfronthosting.co.za>
2008-10-13 13:31:13timehorselinkissue1708652 messages
2008-10-13 13:31:12timehorsecreate