[Raphaël Hertzog, 2010-09-18] > If you build the packages python-django with only python2.6 installed, you > don't get the same result as if you build it when python2.5 and python2.6 > are installed... this is because the python buildsystem in debhelper > invokes setup.py once for each version and somehow this leads to modules > being installed in versioned directories when it should not.
"versioned directories"? Did you mean shebangs? > As said in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520834#10 > modules should only be built with the current python version. While IMHO we should test them (if other tests are not available, at least by byte-compiling .py files) at build time with all supported Python versions. I'm even thinking about making that a requirement in packages I upload [...] > So I suggest that we build those only with the current python version. what problems do you have with current approach? IIRC debhelper uses --executable already, so shebangs shouldn't be a problem anymore -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100918205932.gf26...@piotro.eu
