2006/1/11, Tony Meyer <[EMAIL PROTECTED]>: > Remember that there has been a lot of discussion about how > ConfigParser should work in the past; for example (ignoring c.l.p): > > <http://mail.python.org/pipermail/python-dev/2004-October/049454.html> > <http://mail.python.org/pipermail/python-dev/2004-October/049527.html> > <http://aspn.activestate.com/ASPN/Mail/Message/python-dev/1483518>
My god. Read it all (which took me near a thermo flask (or whatever you call to an insulated bottle to keep liquids cold or hot) of "mate"!). I see two paths here: - Good one - Bad one No, sorry, seriously: - Rewrite ConfigParser entirely. - Apply my patch. The first option is the better, though it's the one which will take more work. Someone needs to make a PEP. Michael Chermside, in the first mail of the first link that you sent, was working in a solution, but don't know what is done. In this case, both patchs I talked before should be rejected. The second one is the quickest. Both paths solves my problem. I think we should go with the second option in the short term, and with the first one in the long term. What do you think? . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/ _______________________________________________ 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
