PosixPath() constructor should not accept strings with embedded NUL bytes

Open
#66,345 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
operating-systems

Research direction

Start with the PosixPath() constructor behavior described in the issue and review embedded_null_in_path.patch, the existing proposed change. Verify the expected handling of strings containing embedded NUL bytes, then add or update relevant pathlib tests and run them to confirm the constructor rejects those inputs.

Written by the indexing model from the issue text.

Description

3.11 stdlib type-bug
BPO 22147
Nosy @pitrou, @vajrasky, @iritkatriel
Files
  • embedded_null_in_path.patch
    		•

    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 2014-08-05.19:44:08.428>
labels = ['type-bug', 'library', '3.11']
title = 'PosixPath() constructor should not accept strings with embedded NUL bytes'
updated_at = <Date 2021-09-10.22:26:42.024>
user = 'https://bugs.python.org/ischwabacher'

    bugs.python.org fields:

    activity = <Date 2021-09-10.22:26:42.024>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-08-05.19:44:08.428>
creator = 'ischwabacher'
dependencies = []
files = ['36327']
hgrepos = []
issue_num = 22147
keywords = ['patch']
message_count = 5.0
messages = ['224880', '224882', '225095', '225102', '401616']
nosy_count = 4.0
nosy_names = ['pitrou', 'vajrasky', 'ischwabacher', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue22147'
versions = ['Python 3.11']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    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.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.