TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Setuptools version 78.0.1 breaks install of many packages

22 点作者 computronus大约 2 个月前

6 条评论

lopuhin大约 2 个月前
Crazy amount of breakage...<p>Here is a PR which reverts this: <a href="https:&#x2F;&#x2F;github.com&#x2F;pypa&#x2F;setuptools&#x2F;pull&#x2F;4911" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;pypa&#x2F;setuptools&#x2F;pull&#x2F;4911</a><p>Interesting that maintainers of setuptools still only postpone the depreciation date for a year, so we can probably expect more issues like this in the future.
评论 #43555738 未加载
andenacitelli大约 2 个月前
From what I gather this has basically derailed CI for the morning for the majority of places out there. Only workaround is pinning build-time dependencies, which only pip and uv seem to let you do well. Poetry is SOL &#x2F; heavily cache-dependent as to whether it works.
andenacitelli大约 2 个月前
They yanked the relevant change and pushed a new one with a revert, this is now resolved<p>Took them seemingly forever to do. The reversion, sure, that might take a bit to proof, but the yank should have been done way sooner
评论 #43465057 未加载
brtkwr大约 2 个月前
Probably 78.0.0 as well which was released yesterday. The diff between 78.0.0 and 78.0.1 appears to be no-op from user perspective <a href="https:&#x2F;&#x2F;github.com&#x2F;pypa&#x2F;setuptools&#x2F;compare&#x2F;v78.0.0...v78.0.1" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;pypa&#x2F;setuptools&#x2F;compare&#x2F;v78.0.0...v78.0.1</a>
评论 #43472824 未加载
computronus大约 2 个月前
The original report is just for ansible-vault, but comments indicate widespread effects, hence the altered title here.
jarboot大约 2 个月前
The current approach of the maintainers terrifies me -- de facto standards should be respected. Even if something is invalid like `description-file`, if it is present in 12k repos it should raise a warning and not break anything.<p>In the rationale for this that I can find [1], a maintainer says the following:<p>&gt; I&#x27;m inclined to say we should do it, even though it will cause some disruption.<p>They also say an alternative is to &quot;accept the status quo&quot;, which is exactily what they should be doing. I can&#x27;t find maintainers giving a compelling reason not to support this status quo of `long-description` as an alias to `long_description` besides &quot;simplifying code.&quot; Code simplification should never take precedence over massive breakage of compatibility.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;pypa&#x2F;setuptools&#x2F;pull&#x2F;4870#pullrequestreview-2669470154" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;pypa&#x2F;setuptools&#x2F;pull&#x2F;4870#pullrequestrevi...</a>
评论 #43469374 未加载
评论 #43465707 未加载