issue_comments: 939985659
This data as json
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/pydata/xarray/pull/5845#issuecomment-939985659 | https://api.github.com/repos/pydata/xarray/issues/5845 | 939985659 | IC_kwDOAMm_X844Bwr7 | 170287 | 2021-10-11T12:29:19Z | 2021-10-11T12:38:01Z | CONTRIBUTOR | I don't think that noarch packages are restricted to python version selectors any more. I've tested this locally with a dummy recipe like this: ```yaml package: name: {{ name|lower }} version: {{ version }} source: path: . build: noarch: python number: 0 script: "{{ PYTHON }} -m pip install . -vv" requirements: host: - python - pip run: - python - importlib_metadata # [ py < 38] ``` This creates a noarch package as expected with a recent conda/build version. This means you can merge this and still use a noarch package on Conda-forge, which will conditionally install the backport importlib-metadata package for older Python versions. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
1020407925 |