Add copy_directory_metadata parameter to shutil.copytree
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 32073 |
|---|---|
| Nosy | @giampaolo, @desbma |
| PRs |
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 2017-11-18.19:13:26.999>
labels = ['3.7', 'type-feature', 'library']
title = 'Add copy_directory_metadata parameter to shutil.copytree'
updated_at = <Date 2018-08-03.21:34:55.613>
user = 'https://github.com/desbma'
bugs.python.org fields:
activity = <Date 2018-08-03.21:34:55.613>
actor = 'desbma'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-11-18.19:13:26.999>
creator = 'desbma'
dependencies = []
files = []
hgrepos = []
issue_num = 32073
keywords = ['patch']
message_count = 7.0
messages = ['306494', '308628', '323055', '323075', '323077', '323081', '323082']
nosy_count = 2.0
nosy_names = ['giampaolo.rodola', 'desbma']
pr_nums = ['4456']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue32073'
versions = ['Python 3.7']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing PR #4456 and the shutil.copytree entry point to understand the proposed copy_directory_metadata parameter. Done means the requested parameter is supported by copytree and the existing behavior remains clear and covered by the relevant project checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100