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

Consider switching to `src` layout

未關閉
#2,403 2 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

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

研究方向

The package layout change from #2277 is the starting point, so compare the repository tree against the src layout pattern and check the packaging config in pyproject.toml or setup.cfg. Moving the package under src/ touches imports, test discovery and the documentation build, so run the test suite afterwards. Done means the package installs from src/, the tests pass, and the maintainers agree on the final layout.

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

描述

To my mind, src is a separate discussion, and doesn't need to be done in https://github.com/pvlib/pvlib-python/pull/2277, if at all.

I brought it up because it seems to me that the majority of projects that use /tests also use /src. Indeed most of the linked packages on the PyOpenSci reference use /pkg/tests rather than /pkg + /tests. Also pytest docs include examples for either /src + /tests OR /pkg/tests but not /pkg + /tests. Maybe it's ok but I like to follow the more popular patterns unless I know why I am deviating from them.

Originally posted by @wholmgren in #2271

#2277 moved the package from a flat layout to a "halfway-src" layout. We should consider adopting the src layout entirely, as the python community seems broadly agreed that the src layout is beneficial.

主要語言
Python
星號
1.7k
分支
1.2k
平均合併
3 天 18 小時
30 天內合併 PR
13

環境準備

從這裡開始

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

pvlib/pvlib-python 的其他 Issue

查看 pvlib/pvlib-python 的全部 Issue

相似的 Issue

更多 Python Issue

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

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