Output from bugz includes an unwanted escape sequence. This can be see using: $ bugz --help | cat -v ^[[?1034husage: bugz [-h] [--config-file CONFIG_FILE] [--connection CONNECTION] [-b BASE] [-u USER] [-p PASSWORD] [--passwordcmd PASSWORDCMD] [-q] [--columns COLUMNS] [--encoding ENCODING] [--skip-auth] [--version] {attach,attachment,get,login,logout,modify,post,search} ... <-- truncated --> This causes problems when using the bugz output with other programs. For example: $ for BUG in $(bugz --quiet search --assigned-to security@gentoo.org | cut -d' ' -f1); do bugz get $BUG; done
I cannot reproduce problem in your actual use example. copy/pasting that one liner, I get no escape sequences showing in any of the output. Further, it seems to run forever and I had to kill it. ^C only seems to kill the one get, continues with the next... substituting for bugs assigned to me, I get no escape sequences. As for the $ bugz --help | cat -v example. That is from python's argparse module which handles the cli help. It shows for me using python-2.7.4. a prospective gsoc student using python-2.7.1 could not reproduce it. So this example is not a pybugz bug, but an upstream python bug.
I am also unable to reproduce this. If there is still an issue, please file a bug against python; the output you are pointing out comes from the argparse module and not from pybugz directly.
