Message 407174 - 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	gvanrossum
Recipients	eryksun, gvanrossum, keeely, rhettinger, steve.dower, terry.reedy
Date	2021-11-27.22:22:38
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1638051758.74.0.190889721669.issue45870@roundup.psfhosted.org>
In-reply-to

Content
AFAIK the reason command history works in cmd.py on Windows is that it's built into the terminal program. Or maybe into the operating system. Thus, the user can use line editing and history, but there is no API (in Python) to interact with these. I'm sure Steve Dower can explain the exact situation -- it may depend on which Windows version and which terminal program you use (my only recent experience is with winterm on Windows 10). I agree that (once we sort out what works in what versions of Windows and which terminal programs) we should clarify this in the docs.

AFAIK the reason command history works in cmd.py on Windows is that it's built into the terminal program. Or maybe into the operating system.

Thus, the user can use line editing and history, but there is no API (in Python) to interact with these.

I'm sure Steve Dower can explain the exact situation -- it may depend on which Windows version and which terminal program you use (my only recent experience is with winterm on Windows 10).

I agree that (once we sort out what works in what versions of Windows and which terminal programs) we should clarify this in the docs.

History
Date	User	Action	Args
2021-11-27 22:22:38	gvanrossum	set	recipients: + gvanrossum, rhettinger, terry.reedy, eryksun, steve.dower, keeely
2021-11-27 22:22:38	gvanrossum	set	messageid: <1638051758.74.0.190889721669.issue45870@roundup.psfhosted.org>
2021-11-27 22:22:38	gvanrossum	link	issue45870 messages
2021-11-27 22:22:38	gvanrossum	create