Brendan Dolan-Gavitt writes: > Package: python-central > Version: 0.5.1 > Severity: normal > > If the user has changed the symlink to python manually, pyversions may > report malformed version information. For example, if the symlink is > created as ln -s /usr/bin/python2.4 /usr/bin/python, readlink will > return "/usr/bin/python2.4" rather than "python2.4", and pyversions -vd > will report "in/python2.4" rather than "2.4". > > Among other things, this means that pycentral will be unable to > determine the default python version and will set it to None, causing a > crash when trying to remove any package (in my case, python-uno) that > uses pycentral. > > One quick fix would be to replace [6:] by [-3:] in pyversions lines 76, > 86, and 127, or to use os.path.basename.
while this may fix this particular bug, changing the /usr/bin/python symlink by hand introduces a much worse behaviour. - Many extension packages are only available for one particular python version; changing the symlink breaks these dependencies, although dpkg/apt think that the dependencies are fulfilled. - byte code will be compiled for the wrong python version. And maybe other things. It's this reason, that the binary is not handled by alternatives. I will close this report, maybe make this a bit more robust, but it doesn't change anything, that the version should not be changed by hand. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
