Provide python executable compiled with enable-shared
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 领域
- build-system
调研方向
首先阅读 recipe 的多输出配置、build_base.sh、build_shared 和 build_static。检查 conda_build_config.yaml 如何影响 macOS 构建，并查看报告的 tkinter 和共享库失败问题。当受支持的子包提供一个使用 enable-shared 构建的 Python 可执行文件，并通过相关的包测试时，即视为完成。
由索引模型根据 Issue 内容生成。
描述
Comment:
Related: https://github.com/conda-forge/python-feedstock/issues/222#issuecomment-1309248101 .
My use-case: https://github.com/lammps/lammps/issues/3520
This could be provided as a subpackage, say python-shared, and install a python.VERSION_shared that the user could symlink or put in front of $PATH, as needed.
I would have built it myself but I am a bit lost since building this recipe with enable-shared is not being easy.
The usual ways of debugging a failing conda build do not work with this package: conda debug ends up giving me an environment where there's no script to activate the environment and no build script either, perhaps because the recipe has multiple outputs and conda debug does not know what to do with it.
So far had to remove the libpython-static output, make the recipe a single output recipe, move build_base.sh to build.sh, edit out script:build.sh, comment out rm .../libpython(...)$VERSION(...).a in build_shared, and add f to ln -sf ../../libpython${VERABI}.a libpython${VERABI}.a in build_static.
The last hurdle is that after building, conda build packages it, where it alters the paths that libraries/execs refer too ( I'm not very knowledgeable about this) and it fails with this message, which I guess has to do with signing in osx-arm64.
PS: fixed it by editing conda-builld/.../post.py https://github.com/conda/conda-build/issues/4392#issuecomment-1310893278
Tests do not pass (tkinter something), but I installed the package anyways and for my use-case it seems to function
PS: does not. conda_build_config.yaml included in the repo overrode the one I had in my home folder, so it did not pick up on the openssl==1.1 constraint and then when I replaced the python in my installation with the shared one it complained it could not find libssl.3.dylib.
After fixing that, for some reason 'libffi.7.dylib' was required by 'import _ctypes', which I fixed in the install environment by symlinking 'libffi.8.dylib' to 'libffi.7.dylib'.
- 主要语言
- Shell
- 星标
- 47
- 派生
- 112
- 平均合并
- 22 小时 18 分钟
- 30 天内合并 PR
- 14
环境准备
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
conda-forge/python-feedstock 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 88/100
conda-forge/python-feedstock#934 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 48/100
conda-forge/python-feedstock#929 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 25/100
conda-forge/python-feedstock#903 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
conda-forge/python-feedstock#880 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 58/100
conda-forge/python-feedstock#879 ·
维护者通常 1 天内回复
查看 conda-forge/python-feedstock 的全部 Issue
相似的 Issue
-
bot-found bug priority: P3
难度 2/5 1-3 小时 新手友好度 84/100
madenvel/KalinkaPlayer#179 ·
-
documentation
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 86/100
jbaruch/coding-policy#621 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 90/100
mattpocock/skills#1134 ·
-
area:build bug P3
难度 1/5 1 小时以内 新手友好度 92/100
uttrflow/uttrflow-swift#2506 ·
维护者通常 1 天内回复