[main] Split shared Python library to libpython - #894
Conversation
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/31789912087. Examine the logs at this URL for more detail. |
010b93e to
b74a768
Compare
Fixes conda-forge#843 Signed-off-by: Michał Górny <mgorny@quansight.com>
…026.08.12.13.59.02 Other tools: - conda-build 26.7.0 - rattler-build 0.72.2 - rattler-build-conda-compat 1.4.19
|
Rebased after #888. Could you PTAL @conda-forge/python? :) |
|
@conda-forge-admin, please relint |
isuruf
left a comment
There was a problem hiding this comment.
libpython should be a dependency of python for python<3.15 to not break anything downstream
|
Hm. So I guess I need to switch the build order here. Conda can't figure out to build Also, quick question, I just stumbled upon https://github.com/conda-forge/libpython-feedstock/blob/main/recipe/meta.yaml (by looking through the package metadata for existing |
|
We should move feedstocks to use |
|
And repodata-patch existing users of |
split existing `build_base.{sh,bat}` into `build.sh`/`bld.bat` and
`install_base.{sh,bat}`.
This turned into a pretty big operation (and likely still contains bugs). Not sure if this is along the lines of what you had in mind. |
Partial backport of #842, specifically 6eeda71, as suggested in #885. I also picked up another useful commit from the dev branch while rebasing. Once this PR (and a rebased #885) are merged, I'm happy to backport the pair as combined PRs to the maintenance branches.