#Importlib metadata is confusing to use
1 messages · Page 1 of 1 (latest)
you are not the only one. the difference between what is in stdlib and in standalone package makes it harder to integrate
At this point I might just pull in a third-party library to implement plugins. (pluggy?)
Honestly, replacing the stdlib docs with a single link to the RTD docs would be less confusing (obviously not a reasonable change, but just to underscore how the duplication is confusing)
I just need some metadata advertising and discovery, really. No need for hooks.
Importlib.metadata would be perfect if its API was more clearly documented
seriously, if there are going to be API changes, please describe the various API signatures clearly (what is EntryPoints?)
</rant>
I’ll add another point, the implementation uses metaprogramming and isn’t that easy to follow, making things worse because if docs aren’t clear the source is the only thing left
if I'm understanding this correctly, in 3.11 you can index entry_points() by group and that's deprecated. In 3.12, you'll be able to index entry_points() by entry point name instead and that's not deprecated. Bit of a head scratcher that 😛