[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: (again) Why default python is not 2.6 yet?



Sandro Tosi <morph@debian.org> (17/02/2010):
> 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).

So, sorry, but yes, I think the FTBFSes are holding up the transition,
and for a good reason. Hopefully, I guess a few NMUs should do the
trick.

(I might be missing something, I'm a bit laggy buildd-wise since past
week.)

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


Reply to: