[issue1708652] Exact matching

Serhiy Storchaka added the comment: Was implemented as fullmatch() in issue16203. -- nosy: +serhiy.storchaka resolution: rejected -> duplicate superseder: -> Proposal: add re.fullmatch() method ___ Python tracker

[issue1708652] Exact matching

Tom Lynn added the comment: (Sorry to comment on a closed issue, it was closed as I was writing this.) It's not that I'm not convinced of the need, just not of the solution. I still think that there are problems here: a) forgetting any \Z or $ terminator to .match() is easy, b) $ is easily

[issue1708652] Exact matching

Changes by Raymond Hettinger : -- resolution: -> rejected status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailin

[issue1708652] Exact matching

Matthew Barnett added the comment: '$' matches at the end of the string or at a newline at the end of a string (if multiline mode isn't turned on). '\Z' matches only at the end of the string. If not even the OP is convinced of the need, then I have no objection to closing. -- __

[issue1708652] Exact matching

Raymond Hettinger added the comment: Can we close this one? -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailin

[issue1708652] Exact matching

Tom Lynn added the comment: Oh dear, I'm wrong on two fronts (I wish Roundup had post editing). a) foo$ doesn't match the 'foo' part of 'foo\nbar' as I stated above, but does match the 'foo' part of 'foo\n'. b) Obviously shortening an input string can cause it to match. It's still weird thou

[issue1708652] Exact matching

Tom Lynn added the comment: Actually, looking at the second part of the docs for $ (on "foo.$") makes me think the main motivating case here may be a bug in re.match:: >>> re.match('foo$', 'foo\n\n') >>> re.match('foo$', 'foo\n') <_sre.SRE_Match object at 0x00A98678> Shortening an

[issue1708652] Exact matching

Tom Lynn added the comment: I'm still unsure. I think this confusion does cause bugs in real-world code. Perhaps more prominence for \A and \Z in the docs? There's already a section comparing regexps starting '^' with match under "Matching vs Searching". The problem is basically that ^ and

[issue1708652] Exact matching

Georg Brandl added the comment: I'm not sure it really is so useful that it warrants a new regex method. -- nosy: +georg.brandl ___ Python tracker ___

[issue1708652] Exact matching

Tom Lynn added the comment: I don't know whether it should stand, I'm somewhere around 0 on it myself. So I guess that means it shouldn't, since it's easier to add features than remove them. The problem is that once you're aware of the need for it you need it less. In case other people are +1

[issue1708652] Exact matching

R. David Murray added the comment: I would say you should make the call on whether or not it is worth adding. IIUC it would mean there was more than one way to do something (\Z vs 'exact'), so I personally am -0 on the feature request. But I'm not a frequent regex user, so I don't think my

[issue1708652] Exact matching

Matthew Barnett added the comment: Does this request still stand? If so then I'll add it to the new regex module. -- ___ Python tracker ___ ___

[issue1708652] Exact matching

Changes by Mark Lawrence : -- nosy: +mrabarnett ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue1708652] Exact matching

Changes by Georg Brandl : -- versions: +Python 3.2 -Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue1708652] Exact matching

Tom Lynn <[EMAIL PROTECTED]> added the comment: Yes, that's right. The binary aspect of it was something of a red herring, I'm afraid, although I still think that (or parsing in general) is an important use case. The prime motivation it that it's easy to either forget the '\Z' or to use '$' inste

[issue1708652] Exact matching

Jeffrey C. Jacobs <[EMAIL PROTECTED]> added the comment: 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 so

[issue1708652] Exact matching

Changes by Jeffrey C. Jacobs <[EMAIL PROTECTED]>: -- nosy: +timehorse versions: +Python 2.7 ___ Python tracker <[EMAIL PROTECTED]> ___ __