Closed vsoch closed 2 years ago
Hi @vsoch - thanks for the issue. We use the setup.cfg
file to house our package metadata. Are you able to pull the info from there?
@rnjudge based on the error message, I do think the install is using setup.cfg (sorry for not realizing this) and the issue is that the fields are deprecated. E.g., here is the long-description: https://github.com/tern-tools/tern/blob/38d5c7664d41b5163a5a88662824bac13e7db8a3/setup.cfg#L12 which should be renamed to long_description.
I can open a quick PR to test updating these metadata fields.
Suggested change! https://github.com/tern-tools/tern/pull/1085
Thank you for this help! Tern is now added to spack, so people can try out install via there, or if interested in Docker/Singularity containers there is a containerize command to do the same and generate in a dockerfile, or modules too. https://github.com/spack/spack/pull/27599#event-5701960443
Describe the bug I'm creating a package for spack, and we cannot install with the traditional setup.py build because package metadata is missing in te setup.py. I am wondering if it would be possible to add?
To Reproduce Steps to reproduce the behavior:
Error in terminal
see above! I pre-emptively pasted :laughing:
Expected behavior Normally setup.py build should be successful.
Environment you are running Tern on
Ubuntu 20.04, no containers! Python 3.8.12
Thank you!