Am Dienstag, 2. Oktober 2012 15:20:02 UTC+2 schrieb Scott Kitterman: > Since Debian is frozen for the Wheezy release, minor bug fixes like this are > extraordinarily unlikely to be accepted.
is there a chance to upgrade the severity then? i took it from the bug that removed the symlink, but since it being there didn’t break anything, while it not being there breaks all python 2 scripts that have the proper shebang. > It's generally not very difficult to write Python that works with Python or > Python3 in any case (as long as you target 2.6 or greater) so a much better > approach is to write bi-lingual Python and use usr/bin/python in your > shebang. That'll work fine everywere. i’m sorry, but i have to disagree strongly. python 2 is essentially a different language. wide areas of the stdlib have been restructured in 3.0 and only with the just-released python 3.3, we can write string and bytes literals that are the same in both python 2 and 3. (both u"" and b"", never "") any bigger project needs a big amount of compatibility code to be bilingual, and one has to refrain from using certain features (e.g. exception syntax) furthermore, every file needs encoding-directives and __future__ imports, which both clutters the otherwise clean code and is a thing one needs to remember or else “/” suddenly behaves differently, causing silent bugs. --- i’m sure it’s possible to refactor any codebase to be bilingual python 2.7/3.3, but i’m also sure i very definitely don’t want to do it for every script and project i ever create. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
