compiled regex objects' match method offers an optional "pos" parameter described to be roughly equivalent to slicing except for how it treats the "^" operation. See http://docs.python.org/library/re.html#re.RegexObject.search

However, the behavior of lookbehind assertions also differs:

>>> re.compile("(?<=a)b").match("ab", 1)
<_sre.SRE_Match object at 0x...>
>>> re.compile("(?<=a)b").match("ab"[1:])
>>>

This alone might be a documentation bug, but the behavior is also inconsistent with the behavior of lookahead assertions, which do *not* look past the endpos:

>>> re.compile("a(?=b)").match("ab", 0, 1)
>>> re.compile("a(?=b)").match("ab")
<_sre.SRE_Match object at 0x...>
>>>

The documentation says of the 'pos' parameter "This is not completely equivalent to slicing the string" and of the 'endpos' parameter "it will be as if the string is endpos characters long".

In other words, it starts searching at 'pos' but truncates at 'endpos'.

Yes, it's inconsistent, but it's documented.

If it's intended behaviour, then I'd request that the documentation specifically mention lookbehind assertions the way it does with "^".

Saying "it's slightly different" doesn't make clear the ways in which it is different, and that's important for people writing or using regular expressions.

IMHO the documentation is fine as is.  Using pos in combination with lookarounds that match on the beginning/end of the "slice" seems a rather uncommon corner case, and I don't think it's worth documenting it.  Even if it was documented, as a user, I would just try it from the interpreter anyway, rather than checking the docs for some prose to decipher.