Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #45895
| X-Received | by 10.224.53.198 with SMTP id n6mr5471098qag.2.1369404581617; Fri, 24 May 2013 07:09:41 -0700 (PDT) |
|---|---|
| MIME-Version | 1.0 |
| X-Received | by 10.50.82.2 with SMTP id e2mr1892497igy.8.1369404581584; Fri, 24 May 2013 07:09:41 -0700 (PDT) |
| Path | csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!t14no586568qam.0!news-out.google.com!y6ni51184qax.0!nntp.google.com!ch1no955392qab.0!postnews.google.com!li6g2000pbb.googlegroups.com!not-for-mail |
| Newsgroups | comp.lang.python |
| Date | Fri, 24 May 2013 07:09:41 -0700 (PDT) |
| Complaints-To | groups-abuse@google.com |
| Injection-Info | li6g2000pbb.googlegroups.com; posting-host=59.95.18.164; posting-account=mBpa7woAAAAGLEWUUKpmbxm-Quu5D8ui |
| NNTP-Posting-Host | 59.95.18.164 |
| References | <mailman.2062.1369400329.3114.python-list@python.org> |
| User-Agent | G2/1.0 |
| X-HTTP-UserAgent | Mozilla/5.0 (X11; Linux i686; rv:20.0) Gecko/20100101 Firefox/20.0,gzip(gfe) |
| Message-ID | <a9ff7e3a-4e98-4a9f-9c84-db9f8bca3130@li6g2000pbb.googlegroups.com> (permalink) |
| Subject | Re: Utility to locate errors in regular expressions |
| From | rusi <rustompmody@gmail.com> |
| Injection-Date | Fri, 24 May 2013 14:09:41 +0000 |
| Content-Type | text/plain; charset=ISO-8859-1 |
| Content-Transfer-Encoding | quoted-printable |
| Xref | csiph.com comp.lang.python:45895 |
Show key headers only | View raw
On May 24, 5:58 pm, Malte Forkel <malte.for...@berlin.de> wrote: > Finding out why a regular expression does not match a given string can > very tedious. I would like to write a utility that identifies the > sub-expression causing the non-match. My idea is to use a parser to > create a tree representing the complete regular expression. Then I could > simplify the expression by dropping sub-expressions one by one from > right to left and from bottom to top until the remaining regex matches. > The last sub-expression dropped should be (part of) the problem. > > As a first step, I am looking for a parser for Python regular > expressions, or a Python regex grammar to create a parser from. > > But may be my idea is flawed? Or a similar (or better) tools already > exists? Any advice will be highly appreciated! > > Malte python-specific: http://kodos.sourceforge.net/ Online: http://gskinner.com/RegExr/ emacs-specific: re-builder and regex-tool http://bc.tech.coop/blog/071103.html
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Utility to locate errors in regular expressions Malte Forkel <malte.forkel@berlin.de> - 2013-05-24 14:58 +0200
Re: Utility to locate errors in regular expressions Roy Smith <roy@panix.com> - 2013-05-24 09:12 -0400
Re: Utility to locate errors in regular expressions Neil Cerutti <neilc@norwich.edu> - 2013-05-24 13:58 +0000
Re: Utility to locate errors in regular expressions rusi <rustompmody@gmail.com> - 2013-05-24 07:09 -0700
Re: Utility to locate errors in regular expressions Christian Gollwitzer <auriocus@gmx.de> - 2013-05-24 20:21 +0200
csiph-web