13242b8e13
As jaraco notes in bug 1942209 [1]: In the later releases of importlib_metadata [ref], performance of loading entry points has been dramatically improved, including much faster discovery/loading and an in-memory cache for entry points for a running process. These performance gains are measured and tracked in the CI runs for importlib_metadata. If possible, this project should consider removing its own cache in favor of the built-in caching in importlib_metadata (also importlib.metadata in Python 3.10). Doing so should also address #1627906 and would limit the dependencies on the data model (such as construction of EntryPoint objects). [ref] https://importlib-metadata.readthedocs.io/en/latest/history.html importlib-metadata clearly isn't a stable API so anything that allows us to reduce the amount of APIs we are exposed to is a good thing. This does require reintroducing the need for importlib-metadata (the third party lib) in some of the older versions of Python but that's a temporary measure at best that will eventually result in us being closer to upstream. [1] https://bugs.launchpad.net/python-stevedore/+bug/1942209 Signed-off-by: Stephen Finucane <stephenfin@redhat.com> Change-Id: Id962cce270cfbe0517da36babcf123137d803082 |
||
|---|---|---|
| .. | ||
| notes | ||
| source | ||