Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prepare a migration from pluggy hooks to entrypoints #752

Open
RonnyPfannschmidt opened this issue Feb 9, 2023 · 0 comments · May be fixed by #972
Open

prepare a migration from pluggy hooks to entrypoints #752

RonnyPfannschmidt opened this issue Feb 9, 2023 · 0 comments · May be fixed by #972

Comments

@RonnyPfannschmidt
Copy link
Contributor

as hatch uses pluggy mostly to obtain a list of named plugin classes,
we discovered in duscussion on discord that entrypoints may be better

the example taken for input is

[project.entry-points."hatch.hook.metadata"]
vcs =  "hatch_vcs.metadata_hook:VCSMetadataHook"
[project.entry-points."hatch.hook.version_source"]
vcs =  "hatch_vcs.version_source:VCSVersionSource"
[project.entry-points."hatch.hook.build"]
vcs =  "hatch_vcs.build_hook:VCSBuildHook"

tools to supplement the migration may be necessary

a most practical tool would be a app that finds hooks, finds the class names, then uses their definitions and attributes to pre-register the implementations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant