Add more examples to the NEWS/What's New docs
未關閉
還沒有人認領這個 Issue。
good first issue
- 主要語言
- Python
- 星號
- 2.1k
- 分支
- 1k
- 平均合併
- 2 天 12 小時
- 30 天內合併 PR
- 12
描述
I think having a concise list is good, but if we want to elaborate more and clarify we could also provide some examples. An example for this is "a new feature was included in Python 3.13 alpha 1, but got removed in 3.13 beta 2, before the final release of 3.13.".
If we add examples, we could follow the ✔️ good/❌ bad format and do one or two lists with examples like:
✅ the following examples need a NEWS entry: * a new function, method, class, module * a new HOWTO in the documentation * the removal of a deprecated feature * ... ❌ the following examples *don't* need a NEWS entry: * a new feature was included in Python 3.13 alpha 1, but got removed in 3.13 beta 2, > before the final release of 3.13 * a typo fix in the documentation or in a docstring * the addition of a new test method * the removal of a private and internal API * code refactoring of a module with no user-visible effects
Originally posted by @ezio-melotti in https://github.com/python/devguide/pull/1238#discussion_r1417763167
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
找到 issue 引用的 NEWS/What's New 文件,並檢視其中目前對於何時新增 NEWS 項目的指引。加入簡潔的正例和反例,包括列出的 Python 發行、文件、測試、private API 和重構案例。確認這些範例能清楚呈現,並與周圍的指引一致。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- python
- 領域
- documentation
- Issue 類型
- 文件
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 52/100