[issue10551] mimetypes read from the registry should not overwrite standard mime mappings

Shane Harvey added the comment: This issue says "mimetypes read from the registry should not overwrite standard mime mappings". Was this change ever made? the following issue claims that the "HKEY_CLASSES_ROOT\.js\Content Type" registry can still overrides ".js" files:

[issue10551] mimetypes read from the registry should not overwrite standard mime mappings

Change by Irit Katriel : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10551] mimetypes read from the registry should not overwrite standard mime mappings

Irit Katriel added the comment: >From the discussion I conclude that all three issues reported here have been >resolved. If nobody objects I will close this issue. -- nosy: +iritkatriel resolution: not a bug -> out of date status: open -> pending

[issue10551] mimetypes read from the registry should not overwrite standard mime mappings

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10551] mimetypes read from the registry should not overwrite standard mime mappings

Mark Lawrence added the comment: Ben you're correct. The other issues have been addressed in #10162 and #9291 so I believe this can be closed. One 2.7 regression regarding mixed str and unicode objects is addressed in #21652. -- ___ Python

[issue10551] mimetypes read from the registry should not overwrite standard mime mappings

Mark Lawrence added the comment: msg185039 from #4969 also complains about this issue. I agree with the solution put forward in the last sentence of msg172531. If we think this is the best idea I'll work on a patch unless anybody else wants to pick this up. -- nosy: +BreamoreBoy,

[issue10551] mimetypes read from the registry should not overwrite standard mime mappings

Ben Hoyt added the comment: Mark, are you referring to part 3 of this issue, the image/pjpeg type of problem? This was fixed in Python 2.7.6 -- see changeset http://hg.python.org/cpython/rev/e8cead08c556 and http://bugs.python.org/issue15207 --

[issue10551] mimetypes read from the registry should not overwrite standard mime mappings

Changes by Ned Deily n...@acm.org: -- nosy: -ned.deily ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10551 ___ ___ Python-bugs-list mailing list

[issue10551] mimetypes read from the registry should not overwrite standard mime mappings

Ben Hoyt added the comment: This is definitely a real issue, and makes mimetypes.guess_type() useless out of the box on Windows. However, I believe the reason it's broken is that the fix for Issue4969 doesn't actually work, and I'm not sure this is possible with the Windows registry. You

[issue10551] mimetypes read from the registry should not overwrite standard mime mappings

R. David Murray rdmur...@bitdance.com added the comment: Kovid: so essentially what you are saying is that the windows platform is broken with respect to MIME types and with respect to its security model. Why am I not surprised? :) You would have the same problem if software installation

[issue10551] mimetypes read from the registry should not overwrite standard mime mappings

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

[issue10551] mimetypes read from the registry should not overwrite standard mime mappings

R. David Murray rdmur...@bitdance.com added the comment: I would expect that it would not be people new to mimetypes that would have the issues, but people like you for whom the behavior on Windows has changed. And this is indeed a concern. The people involved in making the windows mimetypes

[issue10551] mimetypes read from the registry should not overwrite standard mime mappings

Kovid Goyal ko...@kovidgoyal.net added the comment: I actually had in mind people that (like me) develop primarily on unix and assume that mimetypes works the same way on both windows and unix. Of course, the changed behavior is also a concern. At the very least, I would encourage the

[issue10551] mimetypes read from the registry should not overwrite standard mime mappings

Kovid Goyal ko...@kovidgoyal.net added the comment: I apologize for the multiple issue in the ticket. To my mind they were all basically one issue, stemming from the decision to read mimetypes from the registry. Since there are other tickets for the first two issues, I'll change the summary