Kovid Goyal <ko...@kovidgoyal.net> added the comment:
It is, of course, your decision, but IMO, since the mimetypes database in
windows appears to be always broken, the default behavior of the mimetypes
module in python 2.7 on windows is broken for most (all?) windows installs. For
me personally, it doesn't matter anymore, as I have already fixed calibre, but
it would be surprising/unexpected behavior for someone new to using
mimetypes.py on windows. Certainly, my expectation (perhaps naively) was that
guess_type('image.jpg') would always return 'image/jpeg'.
Users on windows rarely (ever?) modify the registry to change mimetypes. The
only thing that does change mimetypes is installed software, without the users'
knowledge/consent. So treating the registry as a reliable store of mime
information, is not a good idea.
On unix, the knownfiles are system files. I dont know about OS X, but on linux,
since most software is installed by package managers, the package managers
usually have policies that prevent application installs from clobbering system
files. And of course, running userland applications dont have the necessary
privileges to modify the files.
Out of curiosity, what is the upside of reading mimetypes from the registry,
given that it's information cannot be trusted?
And you're most welcome, for calibre :)
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue10551>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
