Improve os.rename documentation and tests

Open
#60,482 37 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

Start by reviewing the historical OSRenameCombinations.py file and the 16278OSRenameDocsTest.patch through V5 patch files linked in the issue. Compare them with the current CPython documentation and tests for os.rename, but first clarify the intended documentation and test changes because the issue does not state acceptance criteria.

Written by the indexing model from the issue text.

Description

docs stdlib tests type-feature
BPO 16278
Nosy @loewis, @terryjreedy, @benjaminp, @ezio-melotti, @asvetlov, @cjerdonek, @rovitotv
Files
  • OSRenameCombinations.py
  • 16278OSRenameDocsTest.patch
  • 16278OSRenameDocsTestV2.patch
  • 16278OSRenameDocsTestV3.patch
  • 16278OSRenameDocsTestV4.patch
  • 16278OSRenameDocsTestV5.patch
  • 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-10-18.17:36:16.053>
    labels = ['tests', 'type-feature', 'library', 'docs']
    title = 'Improve os.rename documentation and tests'
    updated_at = <Date 2014-04-14.21:46:48.587>
    user = 'https://bugs.python.org/DavidBenjamin'
    

    bugs.python.org fields:

    activity = <Date 2014-04-14.21:46:48.587>
    actor = 'orsenthil'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Documentation', 'Library (Lib)', 'Tests']
    creation = <Date 2012-10-18.17:36:16.053>
    creator = 'David.Benjamin'
    dependencies = []
    files = ['27915', '29301', '29362', '29370', '29371', '34097']
    hgrepos = []
    issue_num = 16278
    keywords = ['patch']
    message_count = 36.0
    messages = ['173285', '173410', '173715', '173729', '173820', '174180', '174259', '174265', '174861', '174862', '175043', '175133', '176095', '181991', '182003', '182004', '182005', '182041', '182050', '182051', '182057', '182058', '182074', '182094', '182355', '183416', '183477', '183508', '183865', '183911', '183912', '183915', '190125', '211305', '211306', '211427']
    nosy_count = 9.0
    nosy_names = ['loewis', 'terry.reedy', 'benjamin.peterson', 'ezio.melotti', 'asvetlov', 'chris.jerdonek', 'docs@python', 'Todd.Rovito', 'David.Benjamin']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue16278'
    versions = ['Python 3.4']
    

    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.