Bastian Kleineidam <[EMAIL PROTECTED]> writes:

> Thomas Bushnell BSG schrieb:
>> Why is it necessary to convert anything first?  This is the dispute on
>> the list, and it isn't even addressed on the list.

> When the default Python version changes (ie. the "python" package
> depends on python2.4 instead of python2.3), all packages depending on
> the default python with (<< 2.4) dependencies will have to change. All
> packages depending on a default python with "python2.3-foo" packages
> will also have to change. And there will most likely be regressions,
> some packages will not run with Python 2.4.

You have misunderstood the question.

The question is why we *also* have to convert to a whole new way of
managing python versions.  And, there seem to be *two* competing views
of how to do that.  And there is *no* published consensus on the point.

>> Where is this documented?  Where does this "1-2 week" number come
>> from?

> 1-2 week is just my guess. It seems you are looking for a nice
> time-sheet with tasks and deadlines and weekly status reports "this is
> 55% done" and so forth. I doubt such a thing will ever exist.

No, I want one of the *developers* to say something about it, not just
idle speculation and release-team prognostications.  

How hard is this?  It has now been FIVE MONTHS since Python 2.4 was
ready.

It has been TWO MONTHS since bug #360851 was opened, and the
maintainer ignored it entirely until May 29.  (Nor did he post a word
on debian-python about it.)  And what he said was not even "this is
what we decided at the BOF".  What he said was "read the mailing
list", though, once more, the mailing list *doesn't document the
plans*.

So still, what I want, and what I've been patiently asking for, and am
now impatiently insisting upon, is the Matthias Klose to get off his
rump and bother actually answering the simple question I first asked a
month ago: "What's the status of upgrading the python package to point
at python2.4?"

Thomas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to