[Guido van Rossum] > What sucks (relatively) is the specific way that ConfigParser > provides access to .ini files; I always end up writing a wrapping > layer around it. Unfortunately ConfigParser discourages such wrappers by hiding too much of its implementation as _private attributes (not __class_privates, so they *are* accessible, but even single-underscore _privacy screams "don't touch this -- subject to change without notice"). Back on topic though, I'd like to see +/-'s on the two patches. The first one (http://www.python.org/sf/1017864) is IMO a no-brainer. The second (http://www.python.org/sf/997050) is what I'm really interested in: do we maintain the existing API and functionality, or is it OK to break existing code by *removing* functionality? -- David Goodger <http://python.net/~goodger> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 253 bytes Desc: OpenPGP digital signature Url : http://mail.python.org/pipermail/python-dev/attachments/20041001/c85cd3b4/signature.pgp
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4