Greg Gaughan

barman 1.3.3 seems to now break with argh 0.26 (pre_call seems to no longer work): https://sourceforge.net/p/pgbarman/tickets/56/

Smashing! Thank you. (https://sourceforge.net/p/pgbarman/tickets/56/)

Do you have your PYTHONPATH environment variable set to the pipe2py directory? In Linux this would be something like: ``` export PYTHONPATH=/home/mypath/pipe2py ``` But perhaps `setenv` for Max OS X?

Ah - yes. the pipe2py directory with the `__init__.py` is the package directory, so you'll want: ``` export PYTHONPATH=$PYTHONPATH:/Applications/XAMPP/htdocs/pipeline ```

What do you get when you ``` $ python >>> import sys >>> print sys.path ```

Hmm. Well presumably one of those paths should have the package files in it. Though I wonder what the difference is between the contents of `/Applications/XAMPP/xamppfiles/htdocs/pipeline/test/pipeline` and `/Applications/XAMPP/htdocs/pipeline`. I don't...

So the files seem to be there but they need to be in a package directory named `pipe2py` for the `import pipe2py` to work. So it looks like the files...

I'll make a note to improve the README text - I can see how it could be confusing. Sounds like there could something strange with the pipe definition. I can't...

Sorry - just saw the bit about it being private. It sounds like a regex module parameter is missing - perhaps the loop failed to pass it something to work...

Use the `-s` option to create a .json file created (sorry, not -j), e.g. ``` python compile.py -s -p 2de0e4517ed76082dcddf66f7b218057 ``` (Your earlier `python compile.py pipe_0373e6dbc0f888a2f5af7d342e56eaba.py` will fail: compile.py expects...