replace mode is always on in console

[techtonik]

BPO	17503
Nosy	@amauryfa

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2013-03-21.17:06:09.402>
created_at = <Date 2013-03-21.06:48:11.965>
labels = ['interpreter-core', 'invalid', 'OS-windows']
title = 'replace mode is always on in console'
updated_at = <Date 2013-03-21.17:06:09.401>
user = 'https://bugs.python.org/techtonik'

bugs.python.org fields:

activity = <Date 2013-03-21.17:06:09.401>
actor = 'techtonik'
assignee = 'none'
closed = True
closed_date = <Date 2013-03-21.17:06:09.402>
closer = 'techtonik'
components = ['Interpreter Core', 'Windows']
creation = <Date 2013-03-21.06:48:11.965>
creator = 'techtonik'
dependencies = []
files = []
hgrepos = []
issue_num = 17503
keywords = []
message_count = 6.0
messages = ['184848', '184852', '184853', '184854', '184857', '184886']
nosy_count = 2.0
nosy_names = ['amaury.forgeotdarc', 'techtonik']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue17503'
versions = ['Python 3.1', 'Python 3.2', 'Python 3.3', 'Python 3.4', 'Python 3.5']

[techtonik]

It is very annoying behavior of Python 3.3.0 that when you type in the console, replace mode is always on, and even after you press insert to go insert mode, it resets after every executed line.

Windows Vista 32.
Python 3.3.0 (v3.3.0:bd8afb90ebf2, Sep 29 2012, 10:55:48) [MSC v.1600 32 bit (Intel)] on win32

[techtonik]

In Python 2 replace mode is always off.

[amauryfa]

Python has absolutely no code to control the Windows console. It has always used fgets().

On the other hand, Windows keeps independent settings per shortcut or executable, so if you started Python directly from the start menu (or by opening the python.exe executable from the Explorer), you may have set different options.

To be sure, open a cmd.exe console, and start Python from there. The behavior should be the same in all versions.

[techtonik]

Ok. From cmd.exe both work the same in insert mode, but when I execute them from different shell (http://www.farmanager.com/opensource.php?l=en), the Python 3 starts to misbehave. And Python 2 works ok, because there is pyreadline installed. With -s -S keys it also starts to misbehave.

Any ideas why this external shell affects Python3 and not Python2?

[amauryfa]

I don't know Far Manager. Maybe it starts everything in overwrite mode (and check its console settings)

pyreadline completely overrides Python's input methods and bypasses the console, so behavior is completely independent.

[techtonik]

I've messed with some settings, upgraded Far, restarted it during yet another test and suddenly everything worked. I hate such stuff. Thanks for support.