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 YoSTEALTH
Recipients YoSTEALTH
Date 2018-10-08.22:13:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1539036789.21.0.545547206417.issue34938@psf.upfronthosting.co.za>
In-reply-to
Content
When a user uses from import, there is a flaw in how mimetype.init() updates its global references.

# Option-1 (flawed)
# -----------------
from mimetypes import init, types_map

print(types_map.get('.gz'))  # None
init()  # <- initialize
print(types_map.get('.gz'))  # None

# Option-2
# --------
import mimetypes

print(mimetypes.types_map.get('.gz'))  # None
mimetypes.init()  # <- initialize
print(mimetypes.types_map.get('.gz'))  # application/gzip

As you can see in https://github.com/python/cpython/blob/master/Lib/mimetypes.py#L344 line:358 global reference is reassigned and thus it prevents `from mimetype import types_map` from being updated and using old `types_map` reference.

Potential solution would be to `types_map.update(new dict content)` vs reassigning the variable.
History
Date User Action Args
2018-10-08 22:13:09YoSTEALTHsetrecipients: + YoSTEALTH
2018-10-08 22:13:09YoSTEALTHsetmessageid: <1539036789.21.0.545547206417.issue34938@psf.upfronthosting.co.za>
2018-10-08 22:13:09YoSTEALTHlinkissue34938 messages
2018-10-08 22:13:09YoSTEALTHcreate