Dear Marios,
This probably indicates that the 'packaging' extension is not included
in your Python/3.11.3-GCCcore-12.3.0 installation yet.
We moved around some extensions after the initial easyconfig for
Python/3.11.3-GCCcore-12.3.0 got merged, see
https://github.com/easybuilders/easybuild-easyconfigs/pull/19777.
To fix this, you should run the following command with a recent version
of EasyBuild (4.9.1 or newer) to install the missing extensions in Python:
eb Python-3.11.3-GCCcore-12.3.0.eb --rebuild --skip
regards,
Kenneth
On 18/07/2024 09:42, Marios Constantinou wrote:
Dear all,
I am trying to install hatchling-1.18.0 using the easyconfig
hatchling-1.18.0-GCCcore-12.3.0.eb on an HPC and I get the error below:
Processing
/share/apps/eb/build/hatchling/1.18.0/GCCcore-12.3.0/hatchling/hatchling-1.18.0
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'error'
error: subprocess-exited-with-error
Preparing metadata (pyproject.toml) did not run successfully.
exit code: 1
> [23 lines of output]
Traceback (most recent call last):
File
"/share/apps/eb/software/Python/3.11.3-GCCcore-12.3.0/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
main()
File
"/share/apps/eb/software/Python/3.11.3-GCCcore-12.3.0/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File
"/share/apps/eb/software/Python/3.11.3-GCCcore-12.3.0/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 152, in prepare_metadata_for_build_wheel
whl_basename = backend.build_wheel(metadata_directory,
config_settings)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File
"/share/apps/eb/build/hatchling/1.18.0/GCCcore-12.3.0/hatchling/hatchling-1.18.0/src/hatchling/build.py", line 56, in build_wheel
return os.path.basename(next(builder.build(wheel_directory,
['standard'])))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File
"/share/apps/eb/build/hatchling/1.18.0/GCCcore-12.3.0/hatchling/hatchling-1.18.0/src/hatchling/builders/plugin/interface.py", line 93, in build
self.metadata.validate_fields()
File
"/share/apps/eb/build/hatchling/1.18.0/GCCcore-12.3.0/hatchling/hatchling-1.18.0/src/hatchling/metadata/core.py", line 243, in validate_fields
_ = self.version
^^^^^^^^^^^^
File
"/share/apps/eb/build/hatchling/1.18.0/GCCcore-12.3.0/hatchling/hatchling-1.18.0/src/hatchling/metadata/core.py", line 128, in version
self._version = self._get_version()
^^^^^^^^^^^^^^^^^^^
File
"/share/apps/eb/build/hatchling/1.18.0/GCCcore-12.3.0/hatchling/hatchling-1.18.0/src/hatchling/metadata/core.py", line 232, in _get_version
from packaging.version import InvalidVersion, Version
ModuleNotFoundError: No module named 'packaging'
[end of output]
note: This error originates from a subprocess, and is likely not a
problem with pip.
error: metadata-generation-failed
Encountered error while generating package metadata.
See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
(at easybuild/tools/run.py:682 in parse_cmd_output)
However, installing hatchling-1.18.0 with the GCC-13.2.0 toolchain using
the easyconfig hatchling-1.18.0-GCCcore-13.2.0.eb installs successfully.
On a test system the installation is successful using both toolchains.
I have also checked that both systems have the same python3 packages
installed in the OS.
I will be grateful for any ideas on how to overcome this.
Best Regards,
--
Marios Constantinou,
Systems Administrator
IT Infrastructure Service, University of Cyprus,
1 Panepistimiou ave,CY-2109, Aglantzia
Nicosia - CYPRUS
Tel: +357-22893978
e-mail: [email protected] <mailto:[email protected]>
