You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, in issue #32 I was thrown off-course by the setuptools documentation, which documented both licenseandlicense_files fields.
It was not clear whether the license field was sometimes read from a file instead of being verbatim text, or how the license_files influenced this field.
Experimental work suggested the two fields do not interact; a license file described in license_files does not yield text appearing in the license field. Furthermore, setuptools does not support the file: prefix to denote text as coming from an external file as it does with other fields.
So, in issue #32 I was thrown off-course by the
setuptools
documentation, which documented bothlicense
andlicense_files
fields.It was not clear whether the
license
field was sometimes read from a file instead of being verbatim text, or how thelicense_files
influenced this field.Experimental work suggested the two fields do not interact; a license file described in
license_files
does not yield text appearing in thelicense
field. Furthermore,setuptools
does not support thefile:
prefix to denote text as coming from an external file as it does with other fields.Having seen the library mentioned in issue #74 and reading the official Python package specification linked within (https://packaging.python.org/en/latest/specifications/core-metadata/#license), it is apparent this is a
setuptools
extension, undergoing discussion for inclusion under PEP-639 (https://peps.python.org/pep-0639/).As such, we're probably better off waiting until a decision is made on PEP-639 before implementing it.
The text was updated successfully, but these errors were encountered: