➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients belopolsky, cben, eric.araujo, lesmana, pitrou, r.david.murray
Date 2010-12-09.20:49:06
SpamBayes Score 4.9623814e-05
Marked as misclassified No
Message-id <1291927749.24.0.52550017954.issue5845@psf.upfronthosting.co.za>
In-reply-to
Content 
for what it is worth, I am +1 on having completion and history file work by default.  The sqlite3 command line does this, for example.  I think it is what unix user expect nowadays, and I think it is reasonable.

Looking at my home directory, it would appear that the de-facto standard history file name would be .python_history.  This is based on .mysql_history, .psql_history, and .sqlite_history, none of which I configured explicitly to support history saving.
History
Date User Action Args
2010-12-09 20:49:09r.david.murraysetrecipients: + r.david.murray, cben, belopolsky, pitrou, eric.araujo, lesmana
2010-12-09 20:49:09r.david.murraysetmessageid: <1291927749.24.0.52550017954.issue5845@psf.upfronthosting.co.za>
2010-12-09 20:49:07r.david.murraylinkissue5845 messages
2010-12-09 20:49:07r.david.murraycreate