os.ftruncate on Windows should be sparse
Open
Nobody has claimed this yet.
3.8 (EOL)
3.9 (EOL)
stdlib
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39910 |
|---|---|
| Nosy | @zooba, @Artoria2e5 |
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 2020-03-09.11:19:49.115>
labels = ['3.8', 'library', '3.9']
title = 'os.ftruncate on Windows should be sparse'
updated_at = <Date 2020-03-09.11:19:49.115>
user = 'https://github.com/Artoria2e5'
bugs.python.org fields:
activity = <Date 2020-03-09.11:19:49.115>
actor = 'Artoria2e5'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-03-09.11:19:49.115>
creator = 'Artoria2e5'
dependencies = []
files = []
hgrepos = []
issue_num = 39910
keywords = []
message_count = 1.0
messages = ['363717']
nosy_count = 2.0
nosy_names = ['steve.dower', 'Artoria2e5']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue39910'
versions = ['Python 3.8', 'Python 3.9']
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 tracing the Python os.ftruncate implementation and its Windows-specific behavior; the issue does not name a file or test. Compare the current behavior with Windows sparse-file requirements, then add focused coverage showing that truncation creates a sparse file and confirm the existing os tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100