py2pack failing on jpy

[johanneskastl]

$ py2pack generate -t opensuse.spec -f python-jpy.spec jpy
generating spec file for jpy...
Error: environment variable "JAVA_HOME" must be set to a JDK (>= v1.7) installation directory
/usr/lib/python3.11/site-packages/py2pack/__init__.py:230: UserWarning: Could not get setuptools information from tarball jpy-0.13.0.tar.gz: Command '/usr/bin/python3.11 setup.py -q --command-packages metaextract metaextract -o /tmp/tmpb5eaoj49 ' returned non-zero exit status 1.. Valuable information for the generation might be missing.
  warnings.warn("Could not get setuptools information from tarball {}: {}. "

JAVA_HOME is set (properly?):

$ echo $JAVA_HOME
/usr/lib64/jvm/jre-openjdk
$

Installed packages (on Tumbleweed):

• python311-setuptools_scm-7.1.0-1.2.noarch
• python311-setuptools-67.8.0-1.3.noarch
• python311-py2pack-0.9.0-2.2.noarch

[danigm]

This is because the jpy package has some code in the setup.py that does some checking:

https://github.com/jpy-consortium/jpy/blob/master/setup.py#L104

That's one of the reasons for the setup.py deprecation. But in py2pack we're still using the setup.py when using metaextract to get the information from the python package.

The correct way to solve this issue is to fix in metaextract directly, or look for a replacement for this lib to get the package metadata.

Maybe today it's easier to use directly importlib.metadata and packaging

[johanneskastl]

Thanks for your reply. If I understand you correctly, this means that this needs to be worked around / solved within py2pack?

[s-t-e-v-e-n-k]

It will work if jpyutil is installed -- if you create a venv with py2pack and jpyutil, it will likely work, but I have not tested this. We probably do not want to use importlib.metadata and packaging, but probably project_wheel_metadata from build.util.

[danigm]

Yep, looks like this problem can't be solved either using build.project_wheel_metadata because it produces the same error, it's not possible to build the wheel from the sources for this package, until you have jpyutil. That's the weird thing about setup.py that it can contain any python code, but hopefully, the new pyproject.toml will solve this issue in the future.

In any case, get the metadata from the wheel, or using the build module could be still interesting, because metaextract is a setuptools extension and we're not getting all the metadata from packages that don't use setuptools.

We've some metadata extraction from the pyproject.toml, but not all the fields are the same and each tool can provide this information with a different field or location... So maybe it's a good idea to use the build module to normalize all metadata extraction.