Once you have checked out a copy of pynie, build it as follows:
+ $ setup.py build
This will create a "pynie.pbc" parrot bytecode executable in the
current directory. Pynie doesn't currently have a "install"
To invoke pynie on a Python program from a shell prompt, use:
parrot pynie .pbc foo.py
To run interactively, entering single-line statements:
Note that pynie's interactive mode is not yet up to spec
with Python's interactive mode (it doesn't handle blocks yet).
To run pynie's test suite:
To display the parse tree, add the "--target=parse" option:
parrot pynie .pbc --target=parse foo.py
+ $ pynie --target=parse foo.py
Or, to display the abstract syntax tree, the opcode syntax tree,
or the generated PIR code, use "--target=PAST", "--target=POST",
-The "top" file for the parser is F<pynie.pir> which is used to
-create the F<pynie.pbc> file. It initializes the overall
-parsing system and registers the parser as a Parrot "Pynie" compiler.
+The "top" file for the parser is F<pynie.pir> which is used to create
+the F<pynie.pbc> file and F<pynie> executable. It initializes the
+overall parsing system and registers the parser as a Parrot "Pynie"
The other files needed for the compiler are in the F<src/> subdirectory.
and handed off to the next compilation phases (PAST->POST->PIR)
The PIR files in F<src/builtins> are included as part of
-compiling F<pynie.pir> to produce F<pynie.pbc>.
+compiling F<pynie.pir> to produce F<pynie.pbc>.
The F<pynie.pbc> file can also be used to compile Python code
Patches/bugs/suggestions can be sent to
-Patrick Michaud <firstname.lastname@example.org> is the current author and