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 tlynn
Recipients georg.brandl, loewis, mrabarnett, niemeyer, r.david.murray, timehorse, tlynn
Date 2010-09-18.11:42:16
SpamBayes Score 3.344175e-10
Marked as misclassified No
Message-id <1284810139.38.0.5835450273.issue1708652@psf.upfronthosting.co.za>
In-reply-to
Content
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 $ have weird semantics but are better recognised than \A and \Z.  Looking over the docs again I see that the docs for $ are still misleading, in a way that's related to this issue:

    foo matches both 'foo' and 'foobar', while the regular
    expression foo$ matches only 'foo'.

"foo$ matches only 'foo' (out of 'foo' and 'foobar')" is the correct interpretation of that, but it's easy to read it as "foo$ means exact_match('foo')", which is the misconception I was hoping to put to rest with this (foo$ also matches the 'foo' part of 'foo\nbar', even with flags=0).
History
Date User Action Args
2010-09-18 11:42:19tlynnsetrecipients: + tlynn, loewis, georg.brandl, niemeyer, timehorse, mrabarnett, r.david.murray
2010-09-18 11:42:19tlynnsetmessageid: <1284810139.38.0.5835450273.issue1708652@psf.upfronthosting.co.za>
2010-09-18 11:42:17tlynnlinkissue1708652 messages
2010-09-18 11:42:16tlynncreate