Dynamic metadata: entry-points possible?

[bilke]

Are other dynamic metadata than version and readme possible with scikit-build-core?

The following did not work for me (no error but also no console entry point generated):

[project]
...
dynamic = ["version", "entry-points"]

[tool.setuptools.dynamic]
entry-points = { file = "entry_points.txt" }

[console_scripts]
mycmd = mycmd:main

Or do we need to implement this as a plugin similar to version and readme?

Thanks!

[henryiii]

We don't read tool.setuptools, we are tool.scikit-build. :) It needs to be a plugin, similar to the existing two, yes. It should be very easy to do, even as a local plugin; I'd recommend adding it to scikit-build-core's plugins, though, since the API is still in flux; I will update the integrated plugins as the API changes. If it's local or external, you'll need to require >=0.3,<0.4 (and set tool.scikit-build.experimental=true). More examples are good, though, since I'll be working on a PEP(s) for it soon, and the more use cases we have the better.

[henryiii]

(Unless you are using the experimental setuptools backend, in which case the above should work, we don't touch entry points if setuptools is handling it)

[bilke]

Thanks for the plugin pointers!

Indeed, a local plugin is easy to implement, e.g. for scripts:

from __future__ import annotations

__all__ = ["dynamic_metadata"]


def __dir__() -> list[str]:
    return __all__


def dynamic_metadata(
    fields: frozenset[str],
    settings: dict[str, object] | None = None,
) -> dict[str, str | dict[str, str | None]]:
    if fields != {"scripts"}:
        msg = "Only the 'scripts' field is supported"
        raise ValueError(msg)

    if settings:
        msg = "No inline configuration is supported"
        raise ValueError(msg)

    scripts = {"mycmd": "mycmd:main"}

    return {"scripts": scripts}

I will develop this further for our specific use case and will provide a generalized plugin soon...

[njzjz]

Just curious if there is a timeline to make the API stable, or have a temporary API but keep compatibility with it. It's not good to always use the experimental API.

[henryiii]

scikit-build/dynamic-metadata#21 is the next step.