Disabling logging to ~/.python_history is not simple enough

Open
#65,085 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
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

The issue names no source files, tests, or entry points. Start by reading the original BPO issue 20886 and locating the Python interactive history implementation; done means providing a simpler, documented way to disable logging to ~/.python_history and adding coverage for that behavior.

Written by the indexing model from the issue text.

Description

pending stdlib topic-repl type-feature
BPO 20886
Nosy @pitrou, @jwilk, @merwok, @bitdancer, @vadmium

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-03-10.20:30:35.518>
labels = ['type-feature', 'library']
title = 'Disabling logging to ~/.python_history is not simple enough'
updated_at = <Date 2018-06-01.17:25:59.628>
user = 'https://bugs.python.org/Sworddragon'

bugs.python.org fields:

activity = <Date 2018-06-01.17:25:59.628>
actor = 'jesse.p.ogle'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-03-10.20:30:35.518>
creator = 'Sworddragon'
dependencies = []
files = []
hgrepos = []
issue_num = 20886
keywords = []
message_count = 9.0
messages = ['213079', '213082', '213084', '213107', '213114', '213127', '265568', '265628', '318437']
nosy_count = 8.0
nosy_names = ['pitrou', 'jwilk', 'eric.araujo', 'Arfrever', 'r.david.murray', 'Sworddragon', 'martin.panter', 'jesse.p.ogle']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue20886'
versions = ['Python 3.4']

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.