Naming conventions and guidelines for packages and namespace packages

Open
#59,104 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

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.

Written by the indexing model from the issue text.

Description

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 = []

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.