Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regular expression failure of the sre engine #38919

Closed
grafen mannequin opened this issue Jul 23, 2003 · 3 comments
Closed

Regular expression failure of the sre engine #38919

grafen mannequin opened this issue Jul 23, 2003 · 3 comments

Comments

@grafen
Copy link
Mannequin

grafen mannequin commented Jul 23, 2003

BPO 776311
Files
  • regexfailure.zip: sre regexp testcase infinite loop
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = <Date 2004-09-03.17:23:10.000>
    created_at = <Date 2003-07-23.15:15:57.000>
    labels = ['expert-regex']
    title = 'Regular expression failure of the sre engine'
    updated_at = <Date 2004-09-03.17:23:10.000>
    user = 'https://bugs.python.org/grafen'

    bugs.python.org fields:

    activity = <Date 2004-09-03.17:23:10.000>
    actor = 'niemeyer'
    assignee = 'effbot'
    closed = True
    closed_date = None
    closer = None
    components = ['Regular Expressions']
    creation = <Date 2003-07-23.15:15:57.000>
    creator = 'grafen'
    dependencies = []
    files = ['984']
    hgrepos = []
    issue_num = 776311
    keywords = []
    message_count = 3.0
    messages = ['17306', '17307', '17308']
    nosy_count = 4.0
    nosy_names = ['effbot', 'niemeyer', 'mkc', 'grafen']
    pr_nums = []
    priority = 'normal'
    resolution = 'fixed'
    stage = None
    status = 'closed'
    superseder = None
    type = None
    url = 'https://bugs.python.org/issue776311'
    versions = ['Python 2.2']

    @grafen
    Copy link
    Mannequin Author

    grafen mannequin commented Jul 23, 2003

    Don't depreciate pre as we all will loose a useful
    verification
    tool for sre!

    From time to time I have situations where I wonder why
    re(sre)
    doesn't match its input. Then I change to pre (import
    pre as re)
    and several times it happened that pre worked fine
    while sre did
    not.

    Sorry that I didn't track down the error but if you are
    interested
    in the testcase I attached the test case for you. (This
    failure is
    in a regular expression which maches a complete pattern
    of a
    VHDL Architecture to apply a patch on it so it was
    quick hack
    but a large regex. The other failures I cannot remember
    what it
    was, sorry)

    Regards

    Wolfgang Grafen

    ---------------------------------------
    I will be absent until 5 September 2003
    ---------------------------------------

    @grafen grafen mannequin closed this as completed Jul 23, 2003
    @grafen grafen mannequin assigned effbot Jul 23, 2003
    @grafen grafen mannequin added the topic-regex label Jul 23, 2003
    @grafen grafen mannequin closed this as completed Jul 23, 2003
    @grafen grafen mannequin assigned effbot Jul 23, 2003
    @grafen grafen mannequin added the topic-regex label Jul 23, 2003
    @mkc
    Copy link
    Mannequin

    mkc mannequin commented Aug 29, 2004

    Logged In: YES
    user_id=555

    The particular problem with your test case turned out to be
    an infinite loop in the sre parser. This is fixed in patch
    bpo-1018386.

    If you are aware of or encounter any other cases where sre's
    behavior deviates from pre, please post a bug for them.
    Pending that, I'd suggest this bug be closed.

    Thanks for your excellent bug report!

    @niemeyer
    Copy link
    Mannequin

    niemeyer mannequin commented Sep 3, 2004

    Logged In: YES
    user_id=7887

    Patch bpo-1018386 was applied.

    Thanks for the report! And thanks again for the patch, Mike!

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 9, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    None yet
    Development

    No branches or pull requests

    0 participants