* Cyril Brulebois <kibi@debian.org>, 2010-02-17, 00:32:
No, don't tell me it's because of the first round of binNMUs: either someone's going to fix them or they will be FTBFS with 2.6 as default, and better explicit than implicit (how many people look at those binNMUs except us?).While 2.5 is the default, one can use (with the default interpreter) any package built against 2.5; meaning those FTBFSes don't matter much. Switching to 2.6 would mean that the packages currently FTBFSing can't be used (with the default interpreter).
If python dependencies are generated in a sane way (e.g. using python-support or python-central), such a not-yet-binNMUed package depends on ‘python (<< 2.6)’, so it won't stop working but only prevent upgrade of the default python.
-- Jakub Wilk
Attachment:
signature.asc
Description: Digital signature