os.environ.clear() fails with empty keys (posix.unsetenv)

Open
#64,857 21 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, python
Domain
backend, operating-systems

Research direction

Start with the linked test_empty_env_var.py reproducer and the set_unset_env.c file to understand the empty-key behavior around os.environ.clear() and posix.unsetenv. Confirm the intended behavior from the existing issue discussion, then add regression coverage and verify that clearing the environment handles empty keys consistently.

Written by the indexing model from the issue text.

Description

3.11 interpreter-core
BPO 20658
Nosy @pefu, @vstinner, @blueyed, @ned-deily, @4kir4, @serhiy-storchaka, @iritkatriel
Files
  • test_empty_env_var.py
  • reject_empty_env_var.patch
  • set_unset_env.c
    		•

    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-02-17.13:06:08.225>
labels = ['interpreter-core', '3.11']
title = 'os.environ.clear() fails with empty keys (posix.unsetenv)'
updated_at = <Date 2021-09-04.11:19:31.059>
user = 'https://github.com/blueyed'

    bugs.python.org fields:

    activity = <Date 2021-09-04.11:19:31.059>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2014-02-17.13:06:08.225>
creator = 'blueyed'
dependencies = []
files = ['34132', '34133', '50245']
hgrepos = []
issue_num = 20658
keywords = ['patch']
message_count = 21.0
messages = ['211415', '211450', '211451', '211508', '211509', '211612', '211613', '211615', '211617', '211619', '211622', '211624', '212405', '400467', '400609', '400610', '400611', '400613', '400616', '401037', '401041']
nosy_count = 8.0
nosy_names = ['pefu', 'vstinner', 'blueyed', 'ned.deily', 'Arfrever', 'akira', 'serhiy.storchaka', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'resolved'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue20658'
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.