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 steve.dower
Recipients YoSTEALTH, barry, maxking, r.david.murray, steve.dower, xtreak
Date 2019-10-04.18:18:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1570213080.26.0.8871571263.issue34938@roundup.psfhosted.org>
In-reply-to
Content
Adding email team here, since you were pinged on the PR.

PR 16567 doesn't fix the `inited` member, which is considerably more difficult to do, unfortunately, but it does mean that it's out of sync with the values you hold. Arguably this is a better state to be in though.

Unfortunately, the "internal" data structures referred to in the docs[1] are all documented public API, which means we can't just ignore this issue :( We ought to at least update the docs to mention that `inited` won't be updated if you've `from ... import`ed it (which would normally be obvious, except that now some other values _will_ be updated).

Also, the `init` docs say that it will only be completely rebuilt when `files` is `None` (and specifically calls out passing an empty list as a way to avoid this happening). I'm pretty sure we don't respect this now.

All up, I think we have more work to do here to get the behaviour right. Alternatively, we can make changes in 3.9 to specify better usage (such as explicitly discouraging direct use of the dictionaries and adding more helper functions if necessary).

[1]: https://docs.python.org/3/library/mimetypes.html#mimetypes.init
History
Date User Action Args
2019-10-04 18:18:00steve.dowersetrecipients: + steve.dower, barry, r.david.murray, maxking, YoSTEALTH, xtreak
2019-10-04 18:18:00steve.dowersetmessageid: <1570213080.26.0.8871571263.issue34938@roundup.psfhosted.org>
2019-10-04 18:18:00steve.dowerlinkissue34938 messages
2019-10-04 18:18:00steve.dowercreate