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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

PEP 2026 – Calendar versioning for Python

20 点作者 BerislavLopac7 个月前

4 条评论

xd19367 个月前
I guess I never noticed that they release around once a year.<p><a href="https:&#x2F;&#x2F;devguide.python.org&#x2F;versions&#x2F;" rel="nofollow">https:&#x2F;&#x2F;devguide.python.org&#x2F;versions&#x2F;</a>
评论 #42055290 未加载
tgum7 个月前
I think this is a very cool change<p>also lol:<p><pre><code> &gt; The 3.14 release cycle must go ahead because: [pi].</code></pre>
cozzyd7 个月前
So... what happens in 2126?<p>I suppose we will have python4 by then.
评论 #42056037 未加载
评论 #42055476 未加载
RadiozRadioz7 个月前
If they go through the work of changing the version scheme, I think they should adopt SemVer instead. This CalVer thing is nice for human users for the tasks they listed, however SemVer holds the advantage for machine-run dependency compatibility management. And I&#x27;d argue version numbers in general are used more by people for compatibility than release scheduling.<p>Personally, it is more often that I look to version numbers to gauge compatibility, than any kind of temporal info.
评论 #42056680 未加载
评论 #42056983 未加载
评论 #42056674 未加载