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
There's a great feature by @BastianZim to avoid superfluous selectors in certain cases and encourage noarch.
Unfortunately I just discovered that it requires the --strict-conda-forge flag to enable. Could this be better documented? Or even better could we enable --strict-conda-forge by default?
Also I notice here that the option is not being found because the names are not normalized. In particular, looking with a debugger, I see pkg = 'importlib-metadata >=3.6.0 # [py<310]', so we query info_pkgs on the key importlib-metadata, but info_pkgs only contains importlib_metadata. I don't know where is the proper place to enact the normalization of keys since I don't understand the schema of config.yaml. (This would also be nice to document! For example, why is it called import_name and not pypi_name?)
To Reproduce
grayskull pypi --strict-conda-forge mdformat
Expected behavior
A noarch recipe
Outputs
...
- importlib-metadata >=3.6.0 # [py<310]
...
Environment:
dev environment on main
The text was updated successfully, but these errors were encountered:
Describe the bug
There's a great feature by @BastianZim to avoid superfluous selectors in certain cases and encourage
noarch
.Unfortunately I just discovered that it requires the
--strict-conda-forge
flag to enable. Could this be better documented? Or even better could we enable--strict-conda-forge
by default?Also I notice here that the option is not being found because the names are not normalized. In particular, looking with a debugger, I see
pkg = 'importlib-metadata >=3.6.0 # [py<310]'
, so we queryinfo_pkgs
on the keyimportlib-metadata
, butinfo_pkgs
only containsimportlib_metadata
. I don't know where is the proper place to enact the normalization of keys since I don't understand the schema ofconfig.yaml
. (This would also be nice to document! For example, why is it calledimport_name
and notpypi_name
?)To Reproduce
Expected behavior
A noarch recipe
Outputs
Environment:
dev environment on main
The text was updated successfully, but these errors were encountered: