pydbgr passes the full, unadulterated sys.argv to the script being debugged. This make it impossible to debug any command-line programs that require arguments.

'pydbgr' appears as the name of the executable (sys.argv[0]) and the actual name of the script appears in the second argument.

For instance, running: pydbgr myscript arg1 arg2 causes sys.argv to be set as follows within the script being debugged: ['/full/path/to/pydbgr', 'myscript', 'arg1', 'arg2'] I would have expected: ['myscript', 'arg1', 'arg2']

Likewise: pydbgr --annotate=3 -- myscript arg1 arg2 produces: ['/full/path/to/pydbgr', '--annotate=3', 'myscript', 'arg1', 'arg2'] where I expected: ['myscript', 'arg1', 'arg2']

I'm using the easy_install version of pydbgr: $ pydbgr --version pydbgr version 0.1.0

with python 2.5: $python --version Python 2.5.2

on Ubuntu Hardy: $ uname -a Linux vermeer 2.6.24-19-generic #1 SMP Fri Jul 11 21:01:46 UTC 2008 x86_64 GNU/Linux

I think this should be fixed in SVN now. If not let me know.