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

Stop providing conda packages?

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
release

调研方向

The issue discusses whether to continue publishing the package through conda-forge, referencing the openeo-feedstock and its build failure for release 0.53.0. Read the linked feedstock pull request and assess the maintenance overhead against the stated alternatives; done means a decision on whether to keep providing conda packages. No repository files or tests are named.

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

描述

collect feedback

Since https://github.com/Open-EO/openeo-python-client/issues/176 the openeo package is also installable through conda.

Question is if doing this is still worth the effort.

It adds additional maintenance overhead, typically just accepting some PR on https://github.com/conda-forge/openeo-feedstock, which is not that much when things work automatically, but when some PR related build is broken, I'm basically lost in tooling and workflow I have no experience with (I don't even use conda as a user).
e.g. there is currently some build problem for the release 0.53.0 (https://github.com/conda-forge/openeo-feedstock/pull/48), and the error looks quite cryptic at the surface.

Regardless, I'm not sure how popular/relevant conda still is, now that uv is grabbing a lot of attention

And on top of that, I also noticed this notification in the error logs:

Did you know? You can install many PyPI packages with conda
using conda-pypi. Get started:
https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/install-packages-from-pypi.html

which is another reason to reconsider spending all the conda effort as the openeo package is a pure python wheel on PyPI that can be installed with new versions of conda as-is

主要语言
Python
星标
219
派生
58
平均合并
2 天 19 小时
30 天内合并 PR
10

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

Open-EO/openeo-python-client 的其他 Issue

查看 Open-EO/openeo-python-client 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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