Python

lp://staging/~pythonregexp2.7/python/issue2636-17

Created by TimeHorse on 2008-09-21 and last modified on 2008-09-24

In the current python Regular Expression engine, Positive (?<=...) and Negative (?<!...) assertions are restricted to fixed-length strings. The proposal here is to support strings of arbitrary length in the Positive and Negative look-behind assertions.

Get this branch:: bzr branch lp://staging/~pythonregexp2.7/python/issue2636-17

Members of Python Regexp 2.7 can upload to this branch. Log in for directions.

Branch merges

No branches dependent on this one.

Related bugs

Link a bug report

Related blueprints

Branch information

Owner:: Python Regexp 2.7

Project:: Python

Status:: Development

Recent revisions

39036. By Jeffrey C. "The TimeHorse" Jacobs <email address hidden> on 2008-09-21: Merged in changes from the core Regexp branch.
39035. By Jeffrey C. "The TimeHorse" Jacobs <email address hidden> on 2008-06-03: Changed the generic VERBOSE flag to be VERBOSE_SRE_ENGINE so that it can
be defined at the make level without potentially interfering with other
modules.
39034. By Jeffrey C. "The TimeHorse" Jacobs <email address hidden> on 2008-05-30: Moving these Documentation changes into their own branch so that the minor
changes will not force the documentation suggestion changes to also be
included; they will now only be included in their own branch, for issue 12.
39033. By Jeffrey C. "The TimeHorse" Jacobs <email address hidden> on 2008-05-29: Replaced tab with spaces.
39032. By Jeffrey C. "The TimeHorse" Jacobs <email address hidden> on 2008-05-29: Better comment for the end of line test.
39031. By Jeffrey C. "The TimeHorse" Jacobs <email address hidden> on 2008-05-24: Merged in changes from the latest python source snapshot.
39030. By Jeffrey C. "The TimeHorse" Jacobs <email address hidden> on 2008-05-22: Fixed some spelling mistakes in the test proceedures.
39029. By Jeffrey C. "The TimeHorse" Jacobs <email address hidden> on 2008-05-22: Added some text to the Library Document about the (?P...) notation in
general and the limitations of (?#...) as per a suggestion by Jim
Jewett.
39028. By Jeffrey C. "The TimeHorse" Jacobs <email address hidden> on 2008-05-16: It is easier to understand the output of a 0 Op Code when it is
instead called FAILURE, as that is really what we are trying to
represent.
39027. By Jeffrey C. "The TimeHorse" Jacobs <email address hidden> on 2008-05-01: Because the Regexp modules are being changed, in order to match the
version between the C and Python code there is a shared constant known
as SRE_MAGIC. A new value has been set for SRE_MAGIC which should be
global to whatever change set is finally accepted for inclusion in
Python 2.6.

Branch metadata

Branch format:: Branch format 6

Repository format:: Bazaar pack repository format 1 with rich root (needs bzr 1.0)

This branch contains Public information

Everyone can see this information.

Subscribers

TimeHorse