os.stat fails for file pending delete on Windows
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 28/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- operating-systems
Research direction
Start with the attached stat-bug.py test case and reproduce the failure on Windows for a file pending deletion. Then trace the os.stat implementation and its Windows-specific behavior. Done means the reported case succeeds and the test case is covered by a regression test.
Written by the indexing model from the issue text.
Description
| BPO | 15556 |
|---|---|
| Nosy | @loewis, @pitrou, @tjguk, @jkloth, @briancurtin, @cjerdonek |
| Files |
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-08-04.16:07:42.396>
labels = ['library', 'OS-windows']
title = 'os.stat fails for file pending delete on Windows'
updated_at = <Date 2013-10-24.20:09:41.067>
user = 'https://github.com/jkloth'
bugs.python.org fields:
activity = <Date 2013-10-24.20:09:41.067>
actor = 'tim.golden'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'Windows']
creation = <Date 2012-08-04.16:07:42.396>
creator = 'jkloth'
dependencies = []
files = ['26687']
hgrepos = []
issue_num = 15556
keywords = []
message_count = 6.0
messages = ['167414', '167415', '167416', '167417', '167418', '201175']
nosy_count = 7.0
nosy_names = ['loewis', 'pitrou', 'tim.golden', 'jkloth', 'brian.curtin', 'jeremy.kloth', 'chris.jerdonek']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue15556'
versions = ['Python 3.3', 'Python 3.4']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100