# lib_users usage: lib_users [-h] [--version] [-m] [-s] [-S] [-i GLOB] [-I LITERAL] lib_users: error: unrecognized arguments: /usr/lib/python-exec/python3.3/lib_users # /usr/lib/python-exec/python3.3/lib_users usage: lib_users [-h] [--version] [-m] [-s] [-S] [-i GLOB] [-I LITERAL] lib_users: error: unrecognized arguments: /usr/lib/python-exec/python3.3/lib_users Is it maybe parsing /all/ arguments, including argv[0]?
*sigh* I suspect it's python-exec trying to be overly clever, turning what _was_ argv[0] into argv[1], which argparse then (rightly) barfs on. I'll investigate.
Actually, I was wrong. It was me misunderstanding how argparse likes its input. Fixed, made v0.9 and moved ebuild accordingly.