This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author michael.foord
Recipients brett.cannon, eric.araujo, fdrake, georg.brandl, lukasz.langa, michael.foord, r.david.murray, rhettinger, till
Date 2010-08-03.15:11:07
SpamBayes Score 3.7795e-05
Marked as misclassified No
Message-id <>
Getting *rid* of the name ConfigParser would be annoying and cause *gratuitous* code breakage.

If we are going to keep the name but get rid of the "unsafe" version then we can only replace it with what is now SafeConfigParser - as it is almost entirely compatible with it. (Modulo the bug fixing "behavioural change".)

So the real choices are:

* leave ConfigParser as it is
* deprecate it but not remove it (so as not to needlessly break code)
* deprecate now and replace with SafeConfigParser later

Only the last of these is a positive step forwards... :-)

(Strongly -1 on introducing *yet another name* to refer to these classes by.)
Date User Action Args
2010-08-03 15:11:09michael.foordsetrecipients: + michael.foord, fdrake, brett.cannon, georg.brandl, rhettinger, eric.araujo, r.david.murray, till, lukasz.langa
2010-08-03 15:11:09michael.foordsetmessageid: <>
2010-08-03 15:11:08michael.foordlinkissue6517 messages
2010-08-03 15:11:07michael.foordcreate