Supply entry points? about importlib_metadata

[jaraco]

In GitLab by @warsaw on May 23, 2018, 21:22

I was thinking that importlib.metadata would provide the names of the entry points, but that a separate package (likely importlib.entrypoints as you say, or something different) would do the actual loading and invoking of the entrypoints. I really haven't thought this out in great detail, but it does seem like we're pretty close!

[jaraco]

In GitLab by @jaraco on Sep 10, 2018, 02:45

This issue may already be addressed:

>>> import importlib_metadata
>>> print(importlib_metadata.distribution('keyring').load_metadata('entrypoints.txt'))
[console_scripts]
keyring = keyring.cli:main

[devpi_client]
keyring = keyring.devpi_client

[keyring.backends]
KWallet = keyring.backends.kwallet
SecretService = keyring.backends.SecretService
Windows = keyring.backends.Windows
macOS = keyring.backends.OS_X

[jaraco]

In GitLab by @warsaw on Sep 10, 2018, 17:34

What about providing a higher level API, like importlib_metadata.entrypoints() which is a ConfigParser instance of the parsed entrypoints.txt file?

[jaraco]

In GitLab by @warsaw on Sep 10, 2018, 17:34

assigned to @warsaw

[jaraco]

In GitLab by @warsaw on Sep 10, 2018, 18:58

mentioned in merge request !4

[jaraco]

In GitLab by @warsaw on Sep 11, 2018, 01:08

closed via merge request !4

[jaraco]

In GitLab by @warsaw on Sep 11, 2018, 01:08

mentioned in commit b55da06