Package: python-sphinx Version: 0.4.2-1 Severity: wishlist Both sphinx-build and sphinx-quicksetup attempt (and fail) to use ansi color sequences, even when TERM=dumb (for example, when run from an emacs shell buffer, or m-x compile. This produces garbage, like this:
^[[01mSphinx v0.4.2, building linkcheck^[[39;49;00m While it does look like I can add -N in the generated Makefile, and thus this is only a wishlist item since I have a workaround - it really shouldn't generate color unless it has *some* indication that it might work - even mooching off of $LSCOLORS would be better than doing it blindly, though it should be enough to look at a TERM or TERMCAP property - or perhaps indirectly via curses.has_colors() which does appear to be able to tell "xterm" from "dumb" successfully. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages python-sphinx depends on: ii libjs-jquery 1.2.6-1 JavaScript library for dynamic web ii python 2.5.2-2 An interactive high-level object-o ii python-central 0.6.8 register and build utility for Pyt ii python-docutils 0.5-2 Utilities for the documentation of ii python-jinja 1.2-2 small but fast and easy to use sta ii python-pygments 0.10-1 syntax highlighting package writte python-sphinx recommends no packages. python-sphinx suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
