I did not kept the numbers
Mon, Aug 3
Having thought about this a bit more, I think using the importlib.resources high-level APIs are better. i.e. this series as-is is fine.
Maybe add an example with | head for completeness?
To reviewers: this was my changeset, I'm not sure how authorship is attributed but I... accept the revision of course.
OMG. When I reviewed this, I thought your assertion that resources.open_binary('mercurial.templates', 'coal/map') is not valid was wrong because the low-level resource reader on the meta path importer does allow relative paths! However, it appears that the open_binary() helper functions limit this! This is yet another example of wonky behavior in these resources APIs. FWIW I've brought many of these to the attention of the core Python people at https://bugs.python.org/issue36128 and https://gitlab.com/python-devs/importlib_resources/-/issues/58 (and a few other places that I can't find the links to).
Typo in the title: s/simply/simplify/
@acezar Do you remember the kind of performance difference we had when adding this? I think it would be interesting to add it to the commit message.
To add to this change, it's also entirely possible that we may never need the trait altogether.