Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

A slimmer python

未关闭
#581 6 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
python
领域
build-system

调研方向

从 issue #581 中描述的依赖关系图以及提议的构建时与环境时行为开始。检查目前如何处理 readline、sqlite 和 tk,然后确定是否可行将它们拆分为独立的 Python 包和一个 core 包。完成的标准是得出明确的实现决策和依赖关系设计。

由索引模型根据 Issue 内容生成。

描述

question
Comment:

I'm wondering if there is enough enthusiasm for having a slim python build. My main motivation is to help ensure that downstream packages that depend on python, also declare the dependencies they have on other libraries. The ones that come to mind are:

  • readline
  • sqlite
  • tk

I'm not sure about the implementation, but maybe we can have a behavior similar to pip, where during the build process they aren't pulled in automatically, but for regular users they are? I know that the pip feature is engrained pretty deep into conda, so maybe it isn't that desirable to use it, but the behavior:

  • At build time, maintainers might have to specify python-readline, python-sqlite, python-tk as part of their dependencies.
  • At environment making time, maybe those are all pulled automatically?

With non-python packages, this has typically resulted in the creation of a "core" package. This would mean that the dependency graph might look like

           /----- python-readline ----\------------------> readline
          /------ python-sqlite -------\-----------------> sqlite
python ------------------------------------ python-core
          \-------python-tk------------/-----------------> tk
```
with `tk`, `sqlite` and `readline` being removed as dependencies from `python-core`.


PS. I know this conversation is quite cyclic in nature but I figured it is time to revive it.
主要语言
Shell
星标
47
派生
114
平均合并
3 天 23 小时
30 天内合并 PR
3

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

conda-forge/python-feedstock 的其他 Issue

查看 conda-forge/python-feedstock 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。