Message 375540 - Python tracker

➜

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	bytecookie
Recipients	bytecookie, steven.daprano
Date	2020-08-17.10:33:46
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1597660426.81.0.201587973074.issue41563@roundup.psfhosted.org>
In-reply-to

Content
> it is your responsibility to set a maximum history length. No, sorry. The problem is not the history file, is the massive slow down it causes. And if you have to utilize a process monitoring tool to find out that the history file is the cause, its not a matter of responsibility . You can only be responsible for something you know of. Still I wonder why this isn't an already widely known problem, or is this a new feature? (I am an seasoned developer but very new to python)

> it is your responsibility to set a maximum history length.

No, sorry. The problem is not the history file, is the massive slow down it causes. And if you have to utilize a process monitoring tool to find out that the history file is the cause, its not a matter of responsibility .
You can only be responsible for something you know of.

Still I wonder why this isn't an already widely known problem, or is this a new feature? (I am an seasoned developer but very new to python)

History
Date	User	Action	Args
2020-08-17 10:33:46	bytecookie	set	recipients: + bytecookie, steven.daprano
2020-08-17 10:33:46	bytecookie	set	messageid: <1597660426.81.0.201587973074.issue41563@roundup.psfhosted.org>
2020-08-17 10:33:46	bytecookie	link	issue41563 messages
2020-08-17 10:33:46	bytecookie	create