python / python/cpython

UNC path normalisation issues on Windows

Open
#90,445 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.11 extension-modules OS-windows type-bug
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 46287
Nosy @pfmoore, @tjguk, @zware, @eryksun, @zooba, @neonene

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 2022-01-06.19:36:40.085>
labels = ['type-bug', 'OS-windows', '3.11']
title = 'UNC path normalisation issues on Windows'
updated_at = <Date 2022-01-14.16:57:46.440>
user = 'https://github.com/zooba'

bugs.python.org fields:

activity = <Date 2022-01-14.16:57:46.440>
actor = 'eryksun'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2022-01-06.19:36:40.085>
creator = 'steve.dower'
dependencies = []
files = []
hgrepos = []
issue_num = 46287
keywords = []
message_count = 4.0
messages = ['409903', '409908', '410056', '410458']
nosy_count = 6.0
nosy_names = ['paul.moore', 'tim.golden', 'zach.ware', 'eryksun', 'steve.dower', 'neonene']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue46287'
versions = ['Python 3.11']

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.

Research direction

No source files, tests, or entry points are named. Start by reviewing the linked BPO issue 46287 and its discussion, then identify the Windows path-handling code and reproduce the UNC normalization behavior; done means the reported issues are fixed with regression coverage.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.