[issue38656] mimetypes for python 3.7.5 fails to detect matroska video

David K. Hess added the comment: @michael-lazar a documentation change seems the path of least resistance given the complicated history of this module. +1 from me. -- ___ Python tracker <https://bugs.python.org/issue38

[issue40139] mimetypes module racy

David K. Hess added the comment: I’m not sure I can shed any light on this particular bug, but I would say that based on my dealings with this module, it is definitely not thread-safe. That means that if you are going to have multiple threads accessing it simultaneously, you really should

[issue38656] mimetypes for python 3.7.5 fails to detect matroska video

David K. Hess added the comment: 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

[issue38656] mimetypes for python 3.7.5 fails to detect matroska video

David K. Hess added the comment: Hi, I'm the author of the commit that's been fingered. Some comments about the behavior being reported First, as pointed out by @xtreak, indeed the mimetypes module uses mimetypes files present on the platform to add to the built in list of mim

[issue4963] mimetypes.guess_extension result changes after mimetypes.init()

David K. Hess added the comment: Thank you Steve! Nice to see this one make it across the finish line. -- ___ Python tracker <https://bugs.python.org/issue4

[issue4963] mimetypes.guess_extension result changes after mimetypes.init()

David K. Hess added the comment: Are there any committers watching this issue that are able to review the PR? https://github.com/python/cpython/pull/3062 It's close to 6 months old now with no action on it. I'm willing to help but doing so and then having the PR gather dust

[issue4963] mimetypes.guess_extension result changes after mimetypes.init()

David K. Hess added the comment: FYI, PR opened: https://github.com/python/cpython/pull/3062 -- ___ Python tracker <http://bugs.python.org/issue4963> ___ ___ Pytho

[issue4963] mimetypes.guess_extension result changes after mimetypes.init()

Changes by David K. Hess : -- pull_requests: +3096 ___ Python tracker <http://bugs.python.org/issue4963> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue4963] mimetypes.guess_extension result changes after mimetypes.init()

David K. Hess added the comment: Pushed more commits so here's a branch compare: https://github.com/python/cpython/compare/master...davidkhess:fix-issue-4963 -- ___ Python tracker <http://bugs.python.org/i

[issue4963] mimetypes.guess_extension result changes after mimetypes.init()

David K. Hess added the comment: Ok, I followed @r.david.murray's advice and decided to take a shot at this. First, I noticed that I couldn't reproduce the non-deterministic behavior that I reported above on the latest code (i.e. pre-3.7). After doing some research it appears th