Package: python-cliapp Version: 0.29-1 Severity: wishlist Hello,
I'm using cliapp for rapidly prototyping a new tool, and I find it inconvenient that IOErrors are reported without a backtrace. Although I understand that would be the right behaviour once the tool is ready for prime time. Django has a 'DEBUG=True' setting in its config, which you disable when you put the code into production. It's used to switch default behaviour from "what the developer would expect" to "what the user would expect". Since cliapp is excellent to speed up development of new tools, a debug=True switch, say, in Application's constructor, or tied to a --debug commandline option that would also set the appropriate loglevel, sounds like a very good idea. Ciao, Enrico -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-cliapp depends on: ii python 2.7.2-10 ii python2.6 2.6.7-4 ii python2.7 2.7.3~rc2-2.1 python-cliapp recommends no packages. Versions of packages python-cliapp suggests: ii libjs-query <none> ii libjs-underscore 1.1.6-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
