How to indicate external dependency in built package (metadata Requires-External, PEP725)

[BlueMagma2]

Since version 1.2 core-metadata support a Requires-External field to indicate to whatever installer that there are non-python dependencies and that the package might not work properly without those: https://packaging.python.org/en/latest/specifications/core-metadata/#requires-external-multiple-use

Draft PEP 725 proposes a pyproject.toml syntax that could be used to generate those line in the METADATA file: https://peps.python.org/pep-0725/

Currently is there any way to have poetry add a Requires-External line in my built package ?
Or maybe a plugin exist for this ?

[radoering]

I don't think there is a built-in way. Metadata is handled in poetry.core.masonry.metadata and as it looks requires_external is not set.

[BlueMagma2]

Thank you for your help, I ended up building a poetry plugin that reads the pyproject.toml and add the Requires-External during build.

I hope poetry will support it natively in the future

[povilasb]

@BlueMagma2 I'd be highly interested in that plugin - have you considered open sourcing it? :)

[BlueMagma2]

My employer agreed to make it public, so here it is: https://gitlab.com/public-corner/poetry-external-dependencies

Please note that in order to pip install the plugin, you need to use the --extra-index-url parameter to add the registry for this project since it is not published to pypi yet.