Package: bpython Version: 0.9.6.2-2 Severity: wishlist
Debian currently has a large number of available Python versions in testing/unstable, such as 2.4, 2.5, 2.6, 3.0, 3.1 and soon 3.2 and 2.7. bpython, by default, uses the default interpreter, but it works with some subset of all of the interpreters that are installed using Debian's packages. It would be really awesome if bpython worked more like python interpreters, in the sense that you would have a number of binaries, such as bpython2.4, bpython2.6, bpython3.1... py3k support might be deferred until later when more testing is done, but apparently it works fine (well enough to warrant going into sid, at least). urwid support does not work because urwid doesn't work on py3k and it won't for the forseeable future, but since urwid isn't the default backend anywhere... I've talked this over with upstream (Trundle (Andreas Stuehrk) to be precise) and we've agreed that doing this for each distribution specifically is probably the right course of action, since figuring out which interpreters are installed and which get to use bpython is specific to each distro. Thanks in advance lvh -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bpython depends on: ii python 2.5.4-9 An interactive high-level object-o ii python-pkg-resources 0.6.10-1 Package Discovery and Resource Acc ii python-pygments 1.3+dfsg-1 syntax highlighting package writte ii python-support 1.0.6.1 automated rebuilding support for P bpython recommends no packages. bpython suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
