[Python-Dev] Dealing with mimetools usage in the stdlib (original) (raw)
Adam Olsen rhamph at gmail.com
Sun Aug 10 08:52:47 CEST 2008
- Previous message: [Python-Dev] Dealing with mimetools usage in the stdlib
- Next message: [Python-Dev] Dealing with mimetools usage in the stdlib
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Aug 9, 2008 at 11:41 PM, Brett Cannon <brett at python.org> wrote:
On my quest to remove warnings raised in 2.6 when Python is run with -3, the issue of dealing with mimetools has come up in terms of backwards-compatibility. For instance, in BaseHTTPServer, the headers attribute on BaseHTTPRequestHandler is an instance of mimetools.Message. But in 3.0 it is an instance of http.client.HTTPMessage.
So my question is, should 2.6 be changed to match 3.0, or should deprecation warnings for mimetools (and possibly other modules) just be silenced so as to not risk breaking backwards-compatibility?
Just silence them. The warnings are an aid for finding bugs, not an excuse to create more bugs.
-- Adam Olsen, aka Rhamphoryncus
- Previous message: [Python-Dev] Dealing with mimetools usage in the stdlib
- Next message: [Python-Dev] Dealing with mimetools usage in the stdlib
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]