[Buildroot] [Bug 13321] utils/scanpypi: fails with packages that define a package’s metadata in setup.cfg

[bugzilla at busybox.net <bugzilla@busybox.net>]

https://bugs.busybox.net/show_bug.cgi?id=13321

--- Comment #2 from Oliwia Zaremba <g.oliwia@gmail.com> ---
To provide more background on this issue: this is the result of PEP-517
(https://www.python.org/dev/peps/pep-0517/) getting a wider adoption. According
to the documentation:
https://setuptools.readthedocs.io/en/latest/setuptools.html#id4 the recommended
approach for Python packages is to define the dependencies decoratively in
setup.cfg. The deprecated calls to setup.py remain backwards compatible by
emulating a dummy setup.py with a setup() method call. In that case the method
is called without any arguments, and this is ultimately the reason
utils/scanpypi script fails for many packages that use this new approach. 

It seems to me that one possible solution to this would be to detect if the
setup.cfg exists and retrieve the package's metadata from it (e.g. using the
read_configuration method from setuptools.config). But I wonder if there exists
a Python native solution to retrieve the metadata (including install_requires
dependencies) from a Python package regardless whether PEP-517 convention is
used or not, and more importantly, without installing that package. Does anyone
know of such mechanism?

Also if anyone found a working solution to this, I would very much appreciate
if it can be shared.

-- 
You are receiving this mail because:
You are on the CC list for the bug.