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 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.20:00:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1380484846.2489.4.camel@fsol>
In-reply-to <>
> When a user is not aware of this new feature and has been implementing
> up to now her/his PYTHONSTARTUP file with the first example given in
> python 3.3 documentation at
> then each new interactive python 3.4 session reads (appending them)
> both history files which are saved on exit. Thus those files double
> their size after each interactive python 3.4 session and pretty soon
> become few mega bytes long with a python start up time that becomes
> quite noticeable.

Interesting. A way to avoid doing this would be to only load history if
no history is already present. Since the sys.__interactivehook__ is
executed after PYTHONSTARTUP, this would allow the latter to take
Date User Action Args
2013-09-29 20:00:50pitrousetrecipients: + 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 20:00:50pitroulinkissue5845 messages
2013-09-29 20:00:50pitroucreate