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
I'm trying to use setuptools-conda to vendor some dependencies for a project I'm working on and have hit a hurdle with LICENSE definitions.
In more modern python packages that use the pyproject.toml, it is valid to define the license meta-data as the license file, resulting in the entire license text being placed inside the package meta-data. One of the packages I'm trying to build uses the CC BY:SA license, which includes quotations in the text. The resulting nested quotations for the about/license entry in the recipe appears to be invalid yaml and causes the build to fail.
Looking at the conda-build docs, it appears the about/license key is exclusively for the license name and the full license text should never be in the recipe itself.
Not sure what the best option to handle these types of cases would be other than another kwarg to dist_conda allowing for manual override of the license key. If that seems a reasonable path, I can knock together a PR.
The text was updated successfully, but these errors were encountered:
I'm trying to use
setuptools-conda
to vendor some dependencies for a project I'm working on and have hit a hurdle with LICENSE definitions.In more modern python packages that use the
pyproject.toml
, it is valid to define thelicense
meta-data as the license file, resulting in the entire license text being placed inside the package meta-data. One of the packages I'm trying to build uses the CC BY:SA license, which includes quotations in the text. The resulting nested quotations for the about/license entry in the recipe appears to be invalid yaml and causes the build to fail.Looking at the conda-build docs, it appears the about/license key is exclusively for the license name and the full license text should never be in the recipe itself.
Not sure what the best option to handle these types of cases would be other than another kwarg to
dist_conda
allowing for manual override of the license key. If that seems a reasonable path, I can knock together a PR.The text was updated successfully, but these errors were encountered: