Writing with the logger to stderr by default prevent of using unix tools like grep for filtering, for example $ catho/catho.py find \* media | grep Animal just print 133652 records from the test catalog.
There is a workaround, redirecting stderr to stdout, but it is not really straight forward.
$ catho/catho.py find \* media 2>&1 >/dev/null | grep Animal
Any other ide apart of the 'ugly' workaround ? maybe we should log with info no ? does warning works ? since we can let logging with error for real problematic issues.
Writing with the logger to stderr by default prevent of using unix tools like grep for filtering, for example
$ catho/catho.py find \* media | grep Animal
just print 133652 records from the test catalog.There is a workaround, redirecting stderr to stdout, but it is not really straight forward.
$ catho/catho.py find \* media 2>&1 >/dev/null | grep Animal