Re: [Python-Dev] Did I miss the decision to untabify all of the C code?

2010-05-06 Thread Alexandre Vassalotti
On Wed, May 5, 2010 at 8:52 PM, Joao S. O. Bueno jsbu...@python.org.br wrote: Python 2.7 is in beta, but not applying such a fix now would probably mean that python 2.x would forever remain with the mixed tabs, since it would make much less sense for such a change in a minor revision (although

Re: [Python-Dev] Did I miss the decision to untabify all of the C code?

2010-05-06 Thread Victor Stinner
Le jeudi 06 mai 2010 08:17:14, Alexandre Vassalotti a écrit : On Wed, May 5, 2010 at 8:52 PM, Joao S. O. Bueno jsbu...@python.org.br wrote: Python 2.7 is in beta, but not applying such a fix now would probably mean that python 2.x would forever remain with the mixed tabs, since it would

Re: [Python-Dev] Running Clang 2.7's static analyzer over the code base

2010-05-06 Thread Victor Stinner
Le mardi 04 mai 2010 07:12:32, Martin v. Löwis a écrit : Will changing the indentation of source files to 4 space indents break patches on the bug tracker? Plain patch will choke, but patch -l might accept them. Tested on posixmodule.c: it works :-) -- Victor Stinner

Re: [Python-Dev] Did I miss the decision to untabify all of the C code?

2010-05-06 Thread Antoine Pitrou
Alexandre Vassalotti alexandre at peadrop.com writes: Since 2.7 is likely the last release of the 2.x series, wouldn't it more productive to spend time improving it instead of wasting time on minor details like indentation? We occasionally waste time on minor details such as code

Re: [Python-Dev] Did I miss the decision to untabify all of the C code?

2010-05-06 Thread Victor Stinner
Le jeudi 06 mai 2010 02:59:26, Eric Smith a écrit : I grant you that it's a largely a mechanized change (except for the a posteriori manual intervention part), but still. Attached patches are the manual interventation parts. 99% of the whole patch only changes the indentation. There is just

Re: [Python-Dev] Fwd: broken mailing list links in PEP(s?)

2010-05-06 Thread Barry Warsaw
On May 05, 2010, at 11:35 AM, James Y Knight wrote: And of course if you're paying attention, you can fix the mbox file (quoting From etc) such that it generates the same numbers as it did the first time. Mailman even has a command for this (I feel like an Apple commercial). You should

[Python-Dev] audience-instructors for Teach Me Python Bugfixing needed

2010-05-06 Thread Catherine Devlin
Hey, everybody... I'm Catherine, a database administrator who makes up excuses to write Python instead. I'm not actually here as a core developer, but as somebody who hopes to become a developer and recruit some more, which brings me to my question: Who lives close enough to Ohio to make it to

Re: [Python-Dev] audience-instructors for Teach Me Python Bugfixing needed

2010-05-06 Thread Doug Hellmann
What an excellent idea! We should have these at *every* regional conference. Doug On May 6, 2010, at 10:47 AM, Catherine Devlin wrote: Hey, everybody... I'm Catherine, a database administrator who makes up excuses to write Python instead. I'm not actually here as a core developer, but

Re: [Python-Dev] Running Clang 2.7's static analyzer over the code base

2010-05-06 Thread Brett Cannon
On Thu, May 6, 2010 at 08:09, Ronald Oussoren ronaldousso...@mac.comwrote: On 5 May, 2010, at 22:56, Brett Cannon wrote: I am done running the analysis over trunk. I will not svnmerge these changes into py3k as the amount of time and effort that would take equates to running the static

[Python-Dev] What's New text on future maintenance

2010-05-06 Thread A.M. Kuchling
FYI: I've just added the text below to the What's New document for 2.7. I wanted to describe how 2.7 will probably be maintained, but didn't want to write anything that sounded like an iron-clad guarantee of a maintenance timespan. Does this text seem like a reasonable set of statements? --amk

Re: [Python-Dev] What's New text on future maintenance

2010-05-06 Thread Ben Finney
A.M. Kuchling a...@amk.ca writes: FYI: I've just added the text below to the What's New document for 2.7. I wanted to describe how 2.7 will probably be maintained, but didn't want to write anything that sounded like an iron-clad guarantee of a maintenance timespan. Does this text seem like a

Re: [Python-Dev] What's New text on future maintenance

2010-05-06 Thread Benjamin Peterson
2010/5/6 A.M. Kuchling a...@amk.ca: FYI: I've just added the text below to the What's New document for 2.7.  I wanted to describe how 2.7 will probably be maintained, but didn't want to write anything that sounded like an iron-clad guarantee of a maintenance timespan.  Does this text seem like

Re: [Python-Dev] What's New text on future maintenance

2010-05-06 Thread Terry Reedy
On 5/6/2010 9:50 PM, A.M. Kuchling wrote: FYI: I've just added the text below to the What's New document for 2.7. I wanted to describe how 2.7 will probably be maintained, but didn't want to write anything that sounded like an iron-clad guarantee of a maintenance timespan. Does this text seem