pathlib.Path.resolve(strict=False) strips final path components
Open
Nobody has claimed this yet.
OS-windows
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38793 |
|---|---|
| Nosy | @brettcannon, @pfmoore, @tjguk, @zware, @zooba |
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 2019-11-14.10:16:42.025>
labels = ['type-bug', 'OS-windows']
title = 'pathlib.Path.resolve(strict=False) strips final path components'
updated_at = <Date 2019-11-14.17:08:39.040>
user = 'https://bugs.python.org/lutecki'
bugs.python.org fields:
activity = <Date 2019-11-14.17:08:39.040>
actor = 'brett.cannon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2019-11-14.10:16:42.025>
creator = 'lutecki'
dependencies = []
files = []
hgrepos = []
issue_num = 38793
keywords = []
message_count = 3.0
messages = ['356589', '356615', '356616']
nosy_count = 6.0
nosy_names = ['brett.cannon', 'paul.moore', 'tim.golden', 'zach.ware', 'steve.dower', 'lutecki']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue38793'
versions = ['Python 3.6']
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 reproducing pathlib.Path.resolve(strict=False) on Windows, using the behavior described in issue 82974 and the linked BPO issue 38793. Inspect the pathlib resolution path only after confirming which final components are stripped; done means unresolved final components are preserved and the relevant regression behavior is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100