Use platform defined data directories instead of ~/.python_history

Open
#88,405 4 comments 16 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
operating-systems

Research direction

No source files or tests are named in the issue body. Start by reviewing PR #26377 and the Python 3.11 library code related to ~/.python_history, then identify the platform data-directory behavior and verify the change with the relevant existing tests.

Written by the indexing model from the issue text.

Description

3.13 stdlib type-feature
BPO 44239
Nosy @oxalica
PRs
  • python/cpython#26377
    		•

    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 2021-05-26.10:58:43.729>
labels = ['type-feature', 'library', '3.11']
title = 'Use platform defined data directories instead of ~/.python_history'
updated_at = <Date 2021-05-26.11:39:53.868>
user = 'https://github.com/oxalica'

    bugs.python.org fields:

    activity = <Date 2021-05-26.11:39:53.868>
actor = 'python-dev'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-05-26.10:58:43.729>
creator = 'oxalica'
dependencies = []
files = []
hgrepos = []
issue_num = 44239
keywords = ['patch']
message_count = 1.0
messages = ['394429']
nosy_count = 2.0
nosy_names = ['python-dev', 'oxalica']
pr_nums = ['26377']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue44239'
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.