[issue20886] Disabling logging to ~/.python_history is not simple enough

Jesse Paul Ogle added the comment: Greetings, I came across this issue while looking into XDG Base Directory Specification. This issue is only tagged with version 3.4, but the underlying issue (not being able to change the history file / size through environment variables) appears to still e

[issue20886] Disabling logging to ~/.python_history is not simple enough

Sworddragon added the comment: I'm assuming this means this must be called on every interactive python instance. If not just correct me. While this might be an enhancement it would still be too inconvenient. Basically something that can be configured permanently for example with ~/.bashrc wou

[issue20886] Disabling logging to ~/.python_history is not simple enough

Martin Panter added the comment: Thanks to Issue 26870, in Python 3.6 you should be able to call readline.set_auto_history(False) to stop entries being added to the history list. Does that change anything here? -- nosy: +martin.panter ___ Python tra

[issue20886] Disabling logging to ~/.python_history is not simple enough

Changes by Jakub Wilk : -- nosy: +jwilk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org

[issue20886] Disabling logging to ~/.python_history is not simple enough

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue20886] Disabling logging to ~/.python_history is not simple enough

Antoine Pitrou added the comment: On mar., 2014-03-11 at 02:38 +, Arfrever Frehtes Taifersar Arahesis wrote: > Arfrever Frehtes Taifersar Arahesis added the comment: > > Antoine Pitrou: > > What sure not the "panic mode" is about, but in any case you can simply > > use e.g. "chmod 111 .pytho

[issue20886] Disabling logging to ~/.python_history is not simple enough

Arfrever Frehtes Taifersar Arahesis added the comment: Antoine Pitrou: > What sure not the "panic mode" is about, but in any case you can simply > use e.g. "chmod 111 .python_history" (which will forbid both reading and > writing the file). It surely does not work: $ rm -f .python_history $ to

[issue20886] Disabling logging to ~/.python_history is not simple enough

Antoine Pitrou added the comment: What sure not the "panic mode" is about, but in any case you can simply use e.g. "chmod 111 .python_history" (which will forbid both reading and writing the file). -- nosy: +pitrou ___ Python tracker

[issue20886] Disabling logging to ~/.python_history is not simple enough

Arfrever Frehtes Taifersar Arahesis added the comment: I would suggest to support PYTHONHISTFILE variable (similar to HISTFILE and LESSHISTFILE) and to not replace file pointed by this variable. This shows that file is being currently replaced: # cp /dev/null .python_history # LC_ALL="C" stat -

[issue20886] Disabling logging to ~/.python_history is not simple enough

R. David Murray added the comment: readline (all uses of readline, not just by python) can be controlled via the '.inputrc' file, which is documented in the readline man page, which should be available if readline is available :) Perhaps this should be mentioned in the paragraph(s) where we t

[issue20886] Disabling logging to ~/.python_history is not simple enough

New submission from Sworddragon: I have noticed that since Python 3.4 the interactive mode does log all commands to ~/.python_history. This caused me to switch into "normal user mode" and look for a solution. With Google I have found the related entry in the documentation: On systems that supp