We consume backstage/mkdocs-techdocs-core via some ancient tooling that uses source tarball's requirements.txt files to recursively discover pip dependencies.
Unfortunately, it can't find the requirements.txt under mkdocs_techdocs_core.egg-info/ and so craps itself.
Would it be possible to publish a source tarball that's actually taken from your github sources, rather than derived? Or to include a requirements.txt in the root of the tarball?
Also noticed that you're using python 3.7 to build; maybe a newer version is better as it includes more metadatain the PKG-INFO fie?
Building with Python 3.10 vs. the tarball fetched from PyPI:
We consume backstage/mkdocs-techdocs-core via some ancient tooling that uses source tarball's requirements.txt files to recursively discover pip dependencies.
Unfortunately, it can't find the requirements.txt under mkdocs_techdocs_core.egg-info/ and so craps itself.
Would it be possible to publish a source tarball that's actually taken from your github sources, rather than derived? Or to include a requirements.txt in the root of the tarball?
Also noticed that you're using python 3.7 to build; maybe a newer version is better as it includes more metadatain the PKG-INFO fie?
Building with Python 3.10 vs. the tarball fetched from PyPI: