On the fly code completion interferes with normal typing

Description

What steps will reproduce the problem?

This may be intended behavior, however, it didn’t happen with 3.X.

With code completion and on the fly code completion turned on (note these are on different panes in preferences, which makes discovery hard), try to type the following function definition in a new editor window.

def f(x):
    return x

The code completion pops up a window with xrange as the completion of the return x. If you are typing quickly (as I do) it will auto-complete x as xrange, yielding

def f(x):
    return xrange

I think 3.x had a way to control whether ENTER auto completes or not, I don’t think I see that in 4 (this issue reporter window is modal, so I can’t check while I am typing this)

Anyway, this may be the intended/desired behavior, but I find it hard to imagine most will find it useful. One may counter that x is a bad variable name, but I only really do math in Python, so x is very common usage.

Versions

• Spyder version: 4.0.0b4
• Python version: 3.7.3
• Qt version: 5.9.6
• PyQt5 version: 5.9.2
• Operating System: Windows 7

Dependencies

pygments >=2.0    :  2.4.2 (OK)
qdarkstyle >=2.6.4:  2.7 (OK)
sphinx >=0.6.6    :  2.1.2 (OK)
pyls >=0.27.0     :  0.28.2 (OK)
nbconvert >=4.0   :  5.5.0 (OK)
pandas >=0.13.1   :  0.25.1 (OK)
numpy >=1.7       :  1.16.4 (OK)
sympy >=0.7.3     :  1.4 (OK)
cython >=0.21     :  0.29.13 (OK)
qtconsole >=4.5.2 :  4.5.4 (OK)
IPython >=4.0     :  7.8.0 (OK)
matplotlib >=2.0.0:  3.1.1 (OK)
pylint >=0.25     :  2.3.1 (OK)

[goanpeca]

@rlabbe yes! as @CAM-Gerlach suggested I was indeed asking you to test it to see if it improved your use case. could you please test using the indications by @CAM-Gerlach ?

Cheers

[CAM-Gerlach]

Completion | Linting | Introspection | Code style | ...

Not to bikeshed over a relatively minor detail, but you might consider swapping the positions of Linting and Introspection so that completion, code style and docstring style are still contiguous (as they are currently) given that all three fall under real-time code analysis.