Re: [Python-Dev] configparser 1.1 - one last bug fix needed

2010-12-14 Thread Steven D'Aprano

Antoine Pitrou wrote:

On Tue, 14 Dec 2010 10:20:04 +1000
Nick Coghlan ncogh...@gmail.com wrote:


+1 from me.

If anyone complains too much, perhaps we can offer to retain the old
ConfigParser as _BuggyConfigParser? (that idea is only partially
tongue-in-cheek...)


Or we can put it in the buggy module which receives all buggy code.


The good thing about that idea is that maintenance of buggy.py will be 
so simple!




--
Steven

___
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] configparser 1.1 - one last bug fix needed

2010-12-14 Thread Fred Drake
On Tue, Dec 14, 2010 at 6:24 AM, Steven D'Aprano st...@pearwood.info wrote:
 The good thing about that idea is that maintenance of buggy.py will be so
 simple!

It's self-describing, and needs no further documentation.  :-)


  -Fred

--
Fred L. Drake, Jr.    fdrake at acm.org
A storm broke loose in my mind.  --Albert Einstein
___
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] configparser 1.1 - one last bug fix needed

2010-12-14 Thread Raymond Hettinger

On Dec 14, 2010, at 3:38 AM, Fred Drake wrote:

 On Tue, Dec 14, 2010 at 6:24 AM, Steven D'Aprano st...@pearwood.info wrote:
 The good thing about that idea is that maintenance of buggy.py will be so
 simple!
 
 It's self-describing, and needs no further documentation.  :-)
 

And psychologically more effective than deprecation.
Anyone writing import buggy probably feels like they
have got some explaining to do :-)


Raymond___
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] configparser 1.1 - one last bug fix needed

2010-12-14 Thread Tim Golden

On 14/12/2010 17:01, Raymond Hettinger wrote:


On Dec 14, 2010, at 3:38 AM, Fred Drake wrote:


On Tue, Dec 14, 2010 at 6:24 AM, Steven D'Apranost...@pearwood.info  wrote:

The good thing about that idea is that maintenance of buggy.py will be so
simple!


It's self-describing, and needs no further documentation.  :-)



And psychologically more effective than deprecation.
Anyone writing import buggy probably feels like they
have got some explaining to do :-)


They might be intro retro-robotics:

  http://www.anf.nildram.co.uk/beebcontrol/buggies/bbc_buggy/index.html

(For those not in the UK, this was a very popular schools
project kit on the back of the famous BBC micro initiative)

TJG
___
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] configparser 1.1 - one last bug fix needed

2010-12-13 Thread Nick Coghlan
+1 from me.

If anyone complains too much, perhaps we can offer to retain the old
ConfigParser as _BuggyConfigParser? (that idea is only partially
tongue-in-cheek...)

Regards,
Nick.

-- 
Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
___
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] configparser 1.1 - one last bug fix needed

2010-12-13 Thread Łukasz Langa
Wiadomość napisana przez Nick Coghlan w dniu 2010-12-14, o godz. 01:20:

 +1 from me.
 
 If anyone complains too much, perhaps we can offer to retain the old 
 ConfigParser as _BuggyConfigParser? (that idea is only partially 
 tongue-in-cheek...)
 

We may leave the LegacyInterpolation class if someone *really* needs to support 
that. That way RawConfigParser(interpolation=LegacyInterpolation()) is 
effectively the old ConfigParser.

-- 
Nondeprecatorily yours,
Łukasz Langa
tel. +48 791 080 144
WWW http://lukasz.langa.pl/

___
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] configparser 1.1 - one last bug fix needed

2010-12-13 Thread Antoine Pitrou
On Tue, 14 Dec 2010 10:20:04 +1000
Nick Coghlan ncogh...@gmail.com wrote:

 +1 from me.
 
 If anyone complains too much, perhaps we can offer to retain the old
 ConfigParser as _BuggyConfigParser? (that idea is only partially
 tongue-in-cheek...)

Or we can put it in the buggy module which receives all buggy code.

Regards

Antoine.


___
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