On Apr 16, 7:25 am, "Paul McGuire" <[EMAIL PROTECTED]> wrote:
>
> long-windedness snipped
Oh, P.S., There is a list parser example included in the pyparsing
examples directory, called parsePythonValue.py. It will parse nested
lists, dicts, and tuples.
-- Paul
--
http://mail.python.org/mailman/
On Apr 16, 3:27 am, "7stud" <[EMAIL PROTECTED]> wrote:
>
> Any tips?
7stud -
Here is the modified code, followed by my comments.
Oh, one general comment - you mention that you are quite facile with
regexp's. pyparsing has a slightly different philosophy from that of
regular expressions, especi
In <[EMAIL PROTECTED]>, 7stud wrote:
> However, all of the beginning examples use a Word() in the parse
> expression, but I couldn't find an adequate explanation of what the
> arguments to Word() are and what they mean. I finally found the
> information buried in one of the many documents--the o
Word("ABC", "def") matches "C", "Added", "Beef"
but not "BB", "ACE", "ADD"
That is just baffling. There's no explanation that the characters
specified in the first string are used to match the first char of a
word and that the characters specified in the second string are used
to match the rest o
Basic Pyparsing
Words and Literals
--
http://mail.python.org/mailman/listinfo/python-list
On Apr 16, 2:06 am, "7stud" <[EMAIL PROTECTED]> wrote:
>
Hmmm. My post got cut off. Here's the rest of it:
I'm pretty facile with regex's, and after looking at some pyparsing
threads over the last week or so, I was interested in trying it.
However, all of the beginning examples use a Word() in
Paul McGuire wrote:
> Me? Push? Boy, a guy posts a couple of examples, tries to help some
> people that are stuck with a problem, and what does he get? Called
> "pushy"? Sheesh!
Hey, I never called you pushy! Ok, maybe I sounded a little harsh--I
was pretty frustrated after all. I guess I sho
Please take a look at the new page added to the pyparsing wiki.
-- Paul
--
http://mail.python.org/mailman/listinfo/python-list
On Apr 15, 8:26 pm, "7stud" <[EMAIL PROTECTED]> wrote:
> To the developer:
>
> 1) I went to the pyparsing wiki to download the pyparsing module and
> try it
> 2) At the wiki, there was no index entry in the table of contents for
> Downloads. After searching around a bit, I finally discovered a t
On Apr 15, 9:16 pm, [EMAIL PROTECTED] (Alex Martelli) wrote:
> 7stud <[EMAIL PROTECTED]> wrote:
> > 1) Even though the download at sourceforge said the file name was:
>
> > pyparsing-1.4.6.tar.gz
>
> > it was downloaded to my Desktop as:
>
> > pyparsing-1.4.6.tar
>
> > Did os x 10.4.7 automatically
7stud <[EMAIL PROTECTED]> wrote:
> 1) Even though the download at sourceforge said the file name was:
>
> pyparsing-1.4.6.tar.gz
>
> it was downloaded to my Desktop as:
>
> pyparsing-1.4.6.tar
>
> Did os x 10.4.7 automatically unzip it for me? .gz means the file was
> compressed with gzip, bu
On Apr 15, 7:41 pm, Steven Bethard <[EMAIL PROTECTED]> wrote:
> 7stud wrote:
> > For as hard as you push pyparsing on this forum, I would think you
> > would make it easier to download and install your module. In my
> > opinion, the wiki should provide detailed installation instructions
> > for a
7stud wrote:
> For as hard as you push pyparsing on this forum, I would think you
> would make it easier to download and install your module. In my
> opinion, the wiki should provide detailed installation instructions
> for all supported os's, and the sourceforge downloading process is too
> comp
To the developer:
1) I went to the pyparsing wiki to download the pyparsing module and
try it
2) At the wiki, there was no index entry in the table of contents for
Downloads. After searching around a bit, I finally discovered a tiny
link buried in some text at the top of the home page.
3) Link
14 matches
Mail list logo
