cc @blink1073 has that not been migrated because shared-data needs to be dynamic?

@jmuchovej can you try https://hatch-jupyter-builder.readthedocs.io/en/latest/source/how_to_guides/migrating_data_files_projects.html?

Hmm... looking at the source for hatch_jupyter_builder (and running the migration on a quick run at setup.py), it's not too clear that those files would, in-fact, be moved to {sys.prefix}/path/to/file.

I'll need to finish preparing this for publishing before I can really test and verify that this works. Will circle back when I'm done with that. 🙂

Thanks for the responsiveness and guidance!

@jmuchovej, you could look at ipykernel for inspiration.

You can run hatch new --init instead of using hatch-jupyter-builder if you aren't currently using jupyter-packaging, and move files around as you need in your build hook, then refer to them by path in your tool.hatch.build.targets.wheel.shared-data metadata.

Has there been any resolution for dynamic shared-data? The static declaration works as expected, but I would need a dynamic way. I would expect something like this could work:

from hatchling.builders.hooks.plugin.interface import BuildHookInterface


class CustomBuildHook(BuildHookInterface):
    def initialize(self, version, build_data):
        build_data['extra_metadata']['shared-data'] = { 'my-folder/to/share': '.' }

But unfortunately, it does not.

The only ugly working solution I came up with is to:

• Set the statictool.hatch.build.targets.wheel.shared-data.
• Create a tmp folder in the initialize hook.
• Copy the necessary files over.
• Clean it up once finished in the finalized hook.

I assume, there is a less hacky solution though.