[Python-Dev] standard library mimetypes module pathologically broken?
Robert Lehmann
stargaming at gmail.com
Sun Aug 2 13:14:05 CEST 2009
More information about the Python-Dev mailing list
Sun Aug 2 13:14:05 CEST 2009
- Previous message: [Python-Dev] standard library mimetypes module pathologically broken?
- Next message: [Python-Dev] pylinting the stdlib
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, 01 Aug 2009 23:37:18 -0700, Jacob Rus wrote: > Here is a somewhat more substantively changed version. This one does > away with the 'inited' flag and the 'init' function, which might be > impossible given that their documented (though I would be extremely > surprised if anyone calls them in third-party code) [snip] There seem to be quite a bunch of high-profile third-party modules relying on this interface, eg. Zope, Plone, TurboGears, and CherryPy. See http://www.google.com/codesearch?q=mimetypes.init+lang%3Apython for a more thorough listing. Given that most of them aren't ported to Python 3 yet, I guess, changing the semantics in 3.x seems not-too-bad to me. HTH, -- Robert "Stargaming" Lehmann
- Previous message: [Python-Dev] standard library mimetypes module pathologically broken?
- Next message: [Python-Dev] pylinting the stdlib
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list