PyREPL does not handle `wRepeatCount` on Windows, causing incorrect 'dead key' behavior

Bug report

Bug description:

PyREPL (introduced in Python 3.13) fails to account for the wRepeatCount field in the KEY_EVENT_RECORD on Windows, resulting in incorrect behavior when keys are pressed repeatedly in the REPL. This issue is reproducible in the Windows Terminal on Windows 10 or 11, specifically when using a keyboard layout with dead keys (e.g., US International layout).

This issue can be bothering as it messes with muscle memory when typing quotes in the new PyREPL (which otherwise is AWESOME!)

Steps to Reproduce:

1. Open Python 3.13+ in the Windows Terminal (NOT in an older conhost.exe-based terminal) on Windows 10 or 11.
2. Use a keyboard layout with dead keys, such as the US International layout.
3. Type a dead key character (e.g., ', ", ^, `, or ~) into the REPL input.
   • Expected behavior: No character is typed, as the dead key is waiting for the next key to combine.
   • Actual behavior: No character is typed, which is correct.
4. Type the same dead key again.
   • Expected behavior: The character corresponding to the dead key should be typed twice.
   • Actual behavior: The character is only typed once.

Root Cause:

The Windows Terminal sends a single key event with wRepeatCount == 2 when a key is pressed repeatedly. PyREPL does not check the wRepeatCount value, so the REPL only processes the key press once. In contrast, conhost.exe-based terminals send two separate key events for the repeated key press, causing the REPL to handle the input correctly in those environments.

Desired Fix:

Modify PyREPL to correctly handle the wRepeatCount value in the KEY_EVENT_RECORD. When wRepeatCount > 1, the corresponding key should be processed the specified number of times to ensure correct handling of repeated key presses.

CPython versions tested on:

3.13, 3.14, CPython main branch

Operating systems tested on:

Windows

Linked PRs

• gh-127948

Start at PyREPL's Windows KEY_EVENT_RECORD input handling and inspect how repeated key events are processed. Reproduce the dead-key behavior in Windows Terminal with a dead-key keyboard layout, then verify that an event with wRepeatCount greater than one produces the expected repeated characters.