Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Enable ruff security, logging and debugging rules (S, T20, LOG, G, DTZ, ERA, TD, FIX, EXE)

未關閉
#3,914 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 2 天內回覆

@anth-volk 已經在處理了。

開始於 2026年10月13日。

  • #3915 來自 @anth-volk —— 未關閉

評估

難度
4/5
預估耗時
3-5 天
新手友好度
18/100
Issue 類型
重構
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
python
領域
backend

研究方向

The payload names no specific files, only the ruff rule groups (S, T20, LOG, G, DTZ, ERA, TD, FIX, EXE) and the S101 asserts, T20 prints, and DTZ datetimes they touch. Start with the ruff configuration in the repository and linked pull request #3915 to see which rules are already enabled and what has been fixed. Done means the new rules pass with each finding either fixed or suppressed with a stated reason, and error responses and published schemas are unchanged.

由索引模型根據 Issue 內容生成。

描述

Phase 1 step 1.8, group 6 of the rules workstream: enable ruff's security, logging and debugging rules (S, T20, LOG, G, DTZ, ERA, TD, FIX, EXE).

  • Security (S): fix each finding, or keep it with an inline reason where it's a false positive (fake secrets in tests, repository commands run by tests, fixed container paths).
  • Asserts outside tests (S101): replace type-narrowing asserts with explicit checks, without changing any error response.
  • Prints (T20): remove debug prints from application code; command-line scripts keep their output, with a reason.
  • Logging (LOG, G): module loggers and lazy formatting, with identical message text.
  • Datetimes (DTZ): never switch a value between naive and aware; keep naive values that must stay naive, with a reason.
  • Leftovers (ERA, TD, FIX, EXE): delete commented-out code, turn TODOs into plain notes or issue links, and match shebangs with the executable bit.

Error responses and published schemas must not change.

主要語言
Python
星號
18
分支
33
平均合併
1 天 20 小時
30 天內合併 PR
27

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

PolicyEngine/policyengine-api 的其他 Issue

查看 PolicyEngine/policyengine-api 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。