Remove libpython output
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- build-system
Research direction
Start with the recipe/*.yaml files and the linked consuming-feedstock pull requests, checking the remaining unchecked consumers first. Done means the libpython output is removed here, all non-archived consumers are updated, existing builds are handled through repodata patches where needed, and obsolete builds are marked broken.
Written by the indexing model from the issue text.
Description
libpython is becoming a real output for the python recipe itself (https://github.com/conda-forge/python-feedstock/pull/894). We need to remove the output here, change all (non-archived) consuming recipes, and then likely repodata-patch existing builds to point to distutils-activate-mingw instead, and mark the old builds as broken.
This search finds 16 non-archived feedstocks that use this:
- https://github.com/conda-forge/anuga-feedstock/pull/24
- https://github.com/conda-forge/awex-feedstock/pull/17
- https://github.com/conda-forge/capytaine-feedstock/pull/53
- https://github.com/conda-forge/eatpy-feedstock/pull/13
- https://github.com/conda-forge/finesse-feedstock/pull/77
- https://github.com/conda-forge/framel-feedstock/pull/51
- https://github.com/conda-forge/gala-feedstock/pull/42
- https://github.com/conda-forge/gdcm-feedstock/pull/69
- https://github.com/conda-forge/nds2-client-swig-feedstock/pull/45
- https://github.com/conda-forge/pygetm-feedstock/pull/39
- https://github.com/conda-forge/pygotm-feedstock/pull/20
- https://github.com/conda-forge/pyhams-feedstock/pull/35
- https://github.com/conda-forge/pyreadr-feedstock/pull/61
- https://github.com/conda-forge/python-quickjs-feedstock/pull/13
- https://github.com/conda-forge/rvlib-feedstock/pull/31
- https://github.com/conda-forge/wisdem-feedstock/pull/109
- Dominant language
- C
- Stars
- 0
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from conda-forge/libpython-feedstock
-
bug
Difficulty 5/5 Over a week Newbie friendliness 25/100
conda-forge/libpython-feedstock#18 · 1 comment ·
All issues in conda-forge/libpython-feedstock
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
hapostgres/pg_auto_failover#1190 ·
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
P3 sonic-vpp
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sonic-net/sonic-buildimage#29662 ·