Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #89586
| Date | 2015-04-29 17:38 -0500 |
|---|---|
| From | Tim Chase <python.list@tim.thechases.com> |
| Subject | Re: Python re to extract useful information from each line |
| References | <e5473ccc-4f7d-431d-93a7-1aeeededcbf0@googlegroups.com> <220dafbc-25f0-48a7-b37a-c8a77a6f2ffa@googlegroups.com> <mhri39$n45$1@ger.gmane.org> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.105.1430349368.3680.python-list@python.org> (permalink) |
On 2015-04-29 14:22, Emile van Sebille wrote:
> On 4/29/2015 1:49 PM, Kashif Rana wrote:
> > pol_elements =
> > re.compile('id\s(?P<p_id>.+?)(?:\sname\s(?P<p_name>.+?))?\sfrom\s(?P<p_from>.+?)\sto\s(?P<p_to>.+?)\s{2}(?P<p_src>[^\s]+?)\s(?P<p_dst>[^\s]+?)\s(?P<p_port>[^\s]+?)(?:(?P<p_nat_status>\snat)\s(?P<p_nat_type>[^\s]+?)(?P<p_nat_ip>\sdip-id\s[^\s]+?)?)?\s(?P<p_action>[^\s]+?)(?:\sschedule\s(?P<p_schedule>[^\s]+?))?(?P<p_log_status>\slog)?$'
> > )
>
> ... and that's why we avoid regular expressions... it makes my head
> hurt just looking at that line noise.
First, it appears the OP isn't using raw strings which make those
back-slashes just ask for trouble.
That said, it would be a lot better if the OP made use of re.VERBOSE
to put each component on its own line:
pol_elements = re.compile(r"""
id
\s
(?P<p_id>.+?)
(?:
\s
name
\s
(?P<p_name>.+?)
)?
\s
from
\s
(?P<p_from>.+?)
\s
to
\s
(?P<p_to>.+?)
\s{2}
(?P<p_src>[^\s]+?)
\s
(?P<p_dst>[^\s]+?)
\s(?P<p_port>[^\s]+?)
(?:
\s
(?P<p_nat_status>nat)
\s
(?P<p_nat_type>\w+)
(
\s?
P<p_nat_src_ip>dip-id
\s
\d+
)?
(
\s
ip
\s
(?P<p_nat_dst_ip>[\d\.]+)
\s
port
(?P<dst_nat_port>\d+)
)?
)?
\s
(?P<p_action>[^\s]+?)
(?:
\s
schedule
\s
(?P<p_schedule>[^\s]+?)
)?
(?P<p_log_status>\slog)?
$
""", re.VERBOSE)
which, with some copious comments in the expression, would make it
almost readable.
Alternatively, switch to an actual parser like pyparsing.
-tkc
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Python re to extract useful information from each line Kashif Rana <kashifrana84@gmail.com> - 2015-04-29 13:42 -0700
Re: Python re to extract useful information from each line Kashif Rana <kashifrana84@gmail.com> - 2015-04-29 13:49 -0700
Re: Python re to extract useful information from each line Emile van Sebille <emile@fenx.com> - 2015-04-29 14:22 -0700
Re: Python re to extract useful information from each line MRAB <python@mrabarnett.plus.com> - 2015-04-29 22:28 +0100
Re: Python re to extract useful information from each line Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-04-29 22:30 +0100
Re: Python re to extract useful information from each line Tim Chase <python.list@tim.thechases.com> - 2015-04-29 17:38 -0500
Re: Python re to extract useful information from each line sohcahtoa82@gmail.com - 2015-04-29 16:29 -0700
Re: Python re to extract useful information from each line Paul McGuire <ptmcg@austin.rr.com> - 2015-08-19 12:53 -0700
csiph-web