Hola Jakub Wilk! El 01/08/2010 a las 00:43 escribiste: > * Maximiliano Curia <m...@debian.org>, 2010-07-31, 19:17: >> The problem is that the packages compiles twice, once for every >> supported python version. But things like plugins have a static >> destination (not dependant of the python version), so its overwritten. > This is not bad per se, as long it's not the default version which is > overwritten.
Makes sense. >> The simplest solution would be to support only one python version at >> any given time. > That would be an unfounded regression. We do want public Python > extensions to be compiled with multiple Python versions. Ok, then probably the best solution would be to set a different destdir for each compilation (that is, for each python version), and treat the default one specially (as a source for the plugin, etc). Would you do it? >> +XS-Python-Version: = 2.6 > Please don't. "XS-Python-Version: = 2.6" is not even valid syntax, > according to Python Policy. Mmmh, and how should I specify a single particular python version? Thanks, see ya. -- "There are only two things wrong with C++: The initial concept and the implementation." -- Bertrand Meyer Saludos /\/\ /\ >< `/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
