Re: [Python-Dev] Python 2.5.3: call for patches
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.5.x release in particular, we > will strictly enforce the "no new features" policy; users interested > in new features should switch to 2.6. 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. Malte ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python 2.5.3: call for patches
> 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 possibility of breaking compilation; such patches are unacceptable. See my comments for details. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python 2.5.3: call for patches
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 patch to 2.5.2. > > It has the possibility of breaking compilation; such patches are > unacceptable. See my comments for details. OK, these should be easy to address. (Comments in the tracker.) Malte ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Backporting multiprocessing?
>> 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 Christian> commit your work to the Google Code repository anytime soon? Folks, My apologies. I have been essentially off-net for the past couple of days. Reason one: we are in the midst of moving. Reason two: our first grandchild (Carmine Michael Montanaro) was born early Friday morning. (yay!) Between visiting Carmine and moving/packing I haven't really been close to a computer since Thursday mid-afternoon. (I'm writing this reply off-net at the moment. Who knows when I'll get back within range of a wireless signal.) I will try to get close enough to the net for a small amount of time Sunday and upload what I have to Google Code. It ain't much, so if you're impatient, you can pretty much replicate what I did: find . -name '*processing*' | egrep -v framework\|build\|PC | xargs tar --create --verbose --file=$HOME/tmp/multiprocessing.tar --exclude=.svn --exclude='*.pyc' Skip ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
