[Python-Dev] bbreport users - please upgrade
Hello, Recently I fixed parsing issues for failures like "hung for 30 minutes", where the last test was no longer detected, since r83543 (the regrtest progress bar, issue #8560). You need to update the script to see the change: http://code.google.com/p/bbreport/ Limitations: - the cache will not be updated, but future builds should be parsed correctly. - there's no documentation yet (except ./bbreport.py --help) -- Florent Xicluna ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] time critical: issue 7902 and 2.6.6rc2
For 2.6.6rc1 a patch was committed that addressed bug 7902: http://bugs.python.org/issue7902 http://svn.python.org/view?rev=81381&view=rev While this fixes a legitimate bug in Python 2.6, it also changes existing behavior in the 2.6 series. As 2.6.6 is the last planned maintenance release, I do not think we've had enough testing of this change and am not sure it should stay in. Note that we've already seen one fallout from this. Issue 9600 was fixed post rc1. While its use of the syntax was incorrect, and the fix was easy and legitimate, I wonder how many other cases in unknown third party code there might be. Antoine in IRC suggests it will be rare, and that the multiprocessing case was probably due to an incomplete code reorganization. I agree, but still. http://bugs.python.org/issue9600 Either way, I think we need a 2.6.6rc2 (a thought that's been invading my dreams all weekend :). This would push back 2.6.6 final to September 12 or 13. I'd like your opinion on whether the fix for 7902 should stay in 2.6.6 or not. Please respond asap, since *if* we revert this, I want that to go into 2.6.6rc2, and I'd like to tag that release in about 6 hours or so. Thanks, -Barry signature.asc Description: PGP signature ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] time critical: issue 7902 and 2.6.6rc2
Sounds to me like the fix is legit, and the bug it uncovered was a real bug and should have been caught. There really is no justification to consider it a feature -- the PEP is clear on that. So I think we should keep the fix. If it is a gray area, it is only gray because the implementation was imperfect, not because one could argue about whether it should be a feature. Anyone who wrote "from .os import walk" thinking it should work did not understand relative imports at all. But more likely such code only happened through some (semi-)automated editing and nobody thought much about it at all, and they would have preferred for it to fail in the first place. All in all it seems pretty clear. --Guido On Mon, Aug 16, 2010 at 8:54 AM, Barry Warsaw wrote: > For 2.6.6rc1 a patch was committed that addressed bug 7902: > > http://bugs.python.org/issue7902 > > http://svn.python.org/view?rev=81381&view=rev > > While this fixes a legitimate bug in Python 2.6, it also changes existing > behavior in the 2.6 series. As 2.6.6 is the last planned maintenance release, > I do not think we've had enough testing of this change and am not sure it > should stay in. > > Note that we've already seen one fallout from this. Issue 9600 was fixed post > rc1. While its use of the syntax was incorrect, and the fix was easy and > legitimate, I wonder how many other cases in unknown third party code there > might be. Antoine in IRC suggests it will be rare, and that the > multiprocessing case was probably due to an incomplete code reorganization. I > agree, but still. > > http://bugs.python.org/issue9600 > > Either way, I think we need a 2.6.6rc2 (a thought that's been invading my > dreams all weekend :). This would push back 2.6.6 final to September 12 or > 13. > > I'd like your opinion on whether the fix for 7902 should stay in 2.6.6 or > not. Please respond asap, since *if* we revert this, I want that to go into > 2.6.6rc2, and I'd like to tag that release in about 6 hours or so. > > Thanks, > -Barry > > ___ > Python-Dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/guido%40python.org > > -- --Guido van Rossum (python.org/~guido) ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] time critical: issue 7902 and 2.6.6rc2
On Aug 16, 2010, at 09:56 AM, Guido van Rossum wrote: >Sounds to me like the fix is legit, and the bug it uncovered was a >real bug and should have been caught. There really is no justification >to consider it a feature -- the PEP is clear on that. So I think we >should keep the fix. Sounds good to me. Thanks for weighing in. -Barry signature.asc Description: PGP signature ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] time critical: issue 7902 and 2.6.6rc2
On Aug 16, 2010, at 11:54 AM, Barry Warsaw wrote: >Either way, I think we need a 2.6.6rc2 (a thought that's been invading >my dreams all weekend :). This would push back 2.6.6 final to >September 12 or 13. Make that 2.6.6 final on August 24. -Barry signature.asc Description: PGP signature ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] time critical: issue 7902 and 2.6.6rc2
On Tue, Aug 17, 2010 at 5:15 AM, Barry Warsaw wrote: > On Aug 16, 2010, at 09:56 AM, Guido van Rossum wrote: > >>Sounds to me like the fix is legit, and the bug it uncovered was a >>real bug and should have been caught. There really is no justification >>to consider it a feature -- the PEP is clear on that. So I think we >>should keep the fix. > > Sounds good to me. Thanks for weighing in. A bit late (since you already cut rc2), but the key point for me is that code that is fixed to work correctly on 2.6.6 (where this bug has been fixed) will still work on any 2.6.x release. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] time critical: issue 7902 and 2.6.6rc2
On Aug 17, 2010, at 09:45 AM, Nick Coghlan wrote: >A bit late (since you already cut rc2), but the key point for me is >that code that is fixed to work correctly on 2.6.6 (where this bug has >been fixed) will still work on any 2.6.x release. Yep, thanks. -Barry signature.asc Description: PGP signature ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] r84124 - in python/branches/py3k: Doc/library/abc.rst Lib/abc.py Lib/test/test_abc.py Misc/NEWS
Am 17.08.2010 02:52, schrieb benjamin.peterson: > Author: benjamin.peterson > Date: Tue Aug 17 02:52:52 2010 > New Revision: 84124 > > Log: > add support for abstract class and static methods #5867 > > Modified: >python/branches/py3k/Doc/library/abc.rst >python/branches/py3k/Lib/abc.py >python/branches/py3k/Lib/test/test_abc.py >python/branches/py3k/Misc/NEWS > > Modified: python/branches/py3k/Doc/library/abc.rst > == > --- python/branches/py3k/Doc/library/abc.rst (original) > +++ python/branches/py3k/Doc/library/abc.rst Tue Aug 17 02:52:52 2010 > @@ -157,6 +157,32 @@ >multiple-inheritance. > > > +.. decorator:: abstractclassmethod(function) versionadded? Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Dev FAQ update request for svnmerge
Could someone who knows how it is currently set up suggest a correction to the dev FAQ for svnmerge usage? The text at http://www.python.org/dev/faq/#how-do-i-merge-between-branches still describes the situation as it was before the trunk was closed to new checkins. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Dev FAQ update request for svnmerge
On Tue, Aug 17, 2010 at 03:08:31PM +1000, Nick Coghlan wrote: > Could someone who knows how it is currently set up suggest a > correction to the dev FAQ for svnmerge usage? 2.26 How do I merge between branches? All development occurs under the py3k branch and bug fixes are expected to be merged into two additional branches, which are release2x-maint and release3x-maint. Assuming a change is committed into py3k as revision 0001, you merge into the release2x-maint by doing: # In the release2x-maint branch checkout. svnmerge.py merge -r 0001 svn commit -F svnmerge-commit-message.txt # r0002 # In a release3x-maint checkout. svnmerge.py merge -r 0001 svn commit -F svnmerge-commit-message.txt # r0003 # Optional In rare situations where you want to backport a security fix or a documentation fix into release26-maint branch: #In the release26-maint checkout. svnmerge merge -S /python/branches/release27-maint -r0002 svn commit -F svnmerge-commit-message.txt # r0004 -- Senthil It's multiple choice time... What is FORTRAN? a: Between thre and fiv tran. b: What two computers engage in before they interface. c: Ridiculous. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
