Naming conventions and guidelines for packages and namespace packages

未關閉
#59,104 6 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
文件
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
python
領域
documentation

研究方向

Start by reviewing the original BPO issue and the attached 4b311ce6624b.diff patch, then inspect the existing Python documentation for packages and namespace packages. Done means the project has agreed, published naming conventions and guidelines covering both package types.

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

描述

docs type-feature
BPO 14899
Nosy @merwok
Files
  • 4b311ce6624b.diff
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = None
    created_at = <Date 2012-05-24.12:42:06.253>
    labels = ['type-feature', 'docs']
    title = 'Naming conventions and guidelines for packages and namespace packages'
    updated_at = <Date 2012-06-27.08:29:55.635>
    user = 'https://bugs.python.org/benoitbryon'
    

    bugs.python.org fields:

    activity = <Date 2012-06-27.08:29:55.635>
    actor = 'benoitbryon'
    assignee = 'docs@python'
    closed = False
    closed_date = None
    closer = None
    components = ['Documentation']
    creation = <Date 2012-05-24.12:42:06.253>
    creator = 'benoitbryon'
    dependencies = []
    files = ['25701']
    hgrepos = ['128']
    issue_num = 14899
    keywords = ['patch']
    message_count = 6.0
    messages = ['161502', '161504', '161505', '161549', '161553', '164128']
    nosy_count = 4.0
    nosy_names = ['eric.araujo', 'docs@python', 'alexis', 'benoitbryon']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue14899'
    versions = []
    

    主要語言
    Python
    星號
    77.2k
    分支
    36k
    平均合併
    1 天 9 小時
    30 天內合併 PR
    558

    貢獻指南

    開啟貢獻指南

    從這裡開始

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

    python/cpython 的其他 Issue

    查看 python/cpython 的全部 Issue

    相似的 Issue

    更多 Python Issue

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

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