Message198653
| Author |
pitrou |
| Recipients |
belopolsky, cben, eric.araujo, ezio.melotti, flox, giampaolo.rodola, larry, lesmana, loewis, mark.dickinson, ned.deily, pitrou, python-dev, r.david.murray, ronaldoussoren, serhiy.storchaka, steven.daprano, techtonik, tshepang, xdegaye |
| Date |
2013年09月29日.21:13:22 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1380489200.2489.5.camel@fsol> |
| In-reply-to |
<1380487424.91.0.689642460736.issue5845@psf.upfronthosting.co.za> |
| Content |
> The patch fixes the problem on my setup. A very minor glitch: after
> manually emptying or removing the PYTHONSTARTUP history file, the
> history is loaded with the content of ~/.python_history on the next
> session.
Yes, the only way to know if a history file has already been loaded with
readline seems to be to query the history itself. So, if the history is
empty, we consider no file has been loaded. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年09月29日 21:13:22 | pitrou | set | recipients:
+ pitrou, loewis, ronaldoussoren, mark.dickinson, cben, belopolsky, larry, techtonik, giampaolo.rodola, ned.deily, ezio.melotti, eric.araujo, steven.daprano, r.david.murray, flox, lesmana, xdegaye, tshepang, python-dev, serhiy.storchaka |
| 2013年09月29日 21:13:22 | pitrou | link | issue5845 messages |
| 2013年09月29日 21:13:22 | pitrou | create |
|