Metadata plugins - #1700
Merged
David-Baddeley merged 2 commits intoAug 27, 2026
Merged
Conversation
Contributor
Author
|
going to go ahead and merge this and re-release as there's a user waiting on the ch-shrinkwrap and the new ch-shrinkwrap installer already uses these endpoints. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses issue #1899
Adds a new and hopefully simpler method of registering plugins by specifying entry points in the plugins pyproject.toml. This means that you can just pip-install the plugin and PYME will find it.
@csoeller @barentine - this should nicely handle the plugin installation workflow for pip based plugins discussed in email.
@zacsimile - Have already ported ch-shrinkwrap
@barentine - Haven't done anything to nep-fitting
Docs below:
Declare entry points in your package's
pyproject.toml. PYME discovers them automatically on startup with nofile copying. This works identically for pip, conda, and editable installs.
The entry point name (left-hand side) is arbitrary and ignored by PYME; the value is the fully qualified module
path. An optional
:attrsuffix (e.g.mypackage.module:some_func) is accepted but only the module path is used.