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 dhess
Recipients The Compiler, ammar2, dhess, r.david.murray, steve.dower, toonn, xtreak
Date 2019-11-18.14:28:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The documentation you quoted does read to me as compatible? The database it is referring to is the one hardcoded in the module – not the one assembled from that and the host OS. But, maybe this is just the vagaries of language and perspective at play.

Anyway I do agree it is an unexpected behavior change from the perspective of a user of the MimeTypes class directly. To get the best context for this change, it's useful to run through the long history of the issue that drove it:

Note, that discussion never touched on the use case of instantiating a MimeTypes class directly and there are apparently no test cases covering this particular scenario either. With no awareness of this perspective/use case it didn't get directly addressed.

Perhaps all MimeTypes instances should auto-load system files unless a new __init__ param selects for this new "clean" behavior?
Date User Action Args
2019-11-18 14:28:07dhesssetrecipients: + dhess, r.david.murray, steve.dower, The Compiler, ammar2, xtreak, toonn
2019-11-18 14:28:07dhesssetmessageid: <>
2019-11-18 14:28:07dhesslinkissue38656 messages
2019-11-18 14:28:07dhesscreate