Please let me know if there's a good place to add tests for this!

This is definitely a short-term fix though, and a better long term solution would be do what cPython does, and have a subclass of SyntaxException errors that indicate that it could be incomplete input. Also, it would probably be better to have the shell just execute code.InteractiveConsole().interact() instead of maintaining two implementations - I'd love to take a stab at that if that's something you'd like to see!

Hopefully once ctypes works _pyrepl will become the default, but this is a good fix.

Actually I would like to test this first locally atleast, since there are no tests by the looks of it.

I'd be happy to add tests if there's already somewhere with tests of the REPL?
If there isn't, I'd also be interested in helping add those, but that seems like it should be a separate PR.

I expected the cpython test-suite to have repl tests, but it doesn't. We don't really need tests I suppose.
I apologize for the confusion.

@arihant2math just to confirm is there anything you need from me to proceed with review? I've got some other patches I'm working on to make this work more generally, and to also enable PY_CF_ALLOW_INCOMPLETE_INPUT in the python parser/compiler

LGTM.
@youknowone please review/merge.

I am sorry. Just distracted a bit by recent CI trouble. The patch looks good

I've got some other patches I'm working on to make this work more generally, and to also enable PY_CF_ALLOW_INCOMPLETE_INPUT in the python parser/compiler

@aneeshdurg Instead of sending patch based on main branch, you can create new branch as many as you want. That helps to create multiple patches at same time.

I fixed comment of codeop.py a bit.

Thank you for contributing!