On Sun, 14 Feb 2010 17:51:29 -0500 Michael Gilbert
<michael.s.gilb...@gmail.com> wrote:
i have tested this in a debian unstable vm running under virtualbox
now, and the problem exists there as well. since, i can only
reproduce this within virtualbox, i am reassigning this bug there.
i've only tested python2.5 at this point, but other python versions > may be
affected as well.
is this still relevnat?
personally I think that failing to build a Python version that has been
unsupported for 13 years on a Debian system that has been unsupported
for 14 years does not warrant a severity "Important".
i have to admit, that I did not try to build an up-to-date version of
Python on an up-to-date Debian VM
gfdarsm
IOhannes
