Martin v. Löwis wrote:
>> Just to emphasize this, "changes" means "bugfixes". (I'm mentioning this
>> mainly because of the people who joined for 2.6/3.0.) For more info,
>> see PEP6 about bugfix releases:
>> http://www.python.org/dev/peps/pep-0006/
>
> Thanks for clarifying this. For the last 2
> May I suggest http://bugs.python.org/issue1040026 ?
>
> It has a fairly simple patch (posixmodule.diff), a new test
> (test_posix5.PATCH), and it fixes a bug that makes os.times unusable on
> common platforms.
In the current form, I'm skeptical about applying this patch to 2.5.2.
It has the po
Martin v. Löwis wrote:
>> May I suggest http://bugs.python.org/issue1040026 ?
>>
>> It has a fairly simple patch (posixmodule.diff), a new test
>> (test_posix5.PATCH), and it fixes a bug that makes os.times unusable on
>> common platforms.
>
> In the current form, I'm skeptical about applying this
>> Maybe doing the modest amount of translation required of the 2.6 unit
>> tests so they run under 0.52 would help. See what fails and then see
>> what fixes correspond to fixing those failing tests.
Christian> Sounds like a good plan. Let's get started! Are you going to
Chr
