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

Generate a "patches" registry? #119

Open
yarikoptic opened this issue Sep 21, 2023 · 1 comment
Open

Generate a "patches" registry? #119

yarikoptic opened this issue Sep 21, 2023 · 1 comment

Comments

@yarikoptic
Copy link
Member

We (well, the https://github.com/datalad/datalad-next/blob/main/datalad_next/patches/__init__.py#L10) have "patch system" in DataLad where extensions might patch core functionality.

The number of patches, their purpose, and their state (proposed to be merged to core or not) across the extensions is not generally known.

Since here we have the registry of extensions, we can centralize harvesting of those patches and creating a table here. Could annotate with versions when patches were introduced, their descriptions etc. But it likely to be useful only in case if we add extra metadata there as is the patch intended to be merged upstream and in what version it was etc.

WDYT?

@mih
Copy link
Member

mih commented Sep 23, 2023

Even without additional metadata this can make sense. The extensions that do patching, do it via an explicit import in <root>.patches.enabled. From that file, things are discoverable.

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

No branches or pull requests

2 participants