 terminates Console in Python Repls

[CoderElijah]

Problem description:
The  character () terminates the console in Python Repls. It is displayed when the program ends however it seems that it also ends the program.

Expected behavior:
I can enter any unicode character without ending a Repl.

Actual behavior:
The  character ends my Repl.

Steps to reproduce:
Create a Python Repl which asks for user input. I used the simple code while True: input() to demonstrate.

Bug appears at this link:
https://replit.com/@CoderElijah/FewRelievedMotion

Browser: Firefox
OS: Arch Linux
Device (Android, iOS, NA leave blank): HP EliteDesk G2 SFF
Desktop app version (Avatar menu->“Version”) or NA: NA
Plan (Free, Hacker, Pro Plan): Hacker

[Spcfork]

My guess is that you’re sending it to the VM, and the client checks for this private use character (probably used for ending the client stream), and ends the client session.

[Firepup650]

The thing is, your code will continue running after you print or input the character, it just Visually looks like it stopped.
I mentioned this a while back as well:

Printing the Replit symbol to the console makes the editor think the program has stopped

Problem description: Printing the Replit symbol used by default in the console () causes the editor to think the program has stopped Expected behavior: The editor knows the program is still running Actual behavior: The editor thinks the program has stopped Steps to reproduce: Option 1: Print/display  to the console observe the Stop button change to Run even though the program is still running Option 2: Use this repl. Observe that the editor assumes the program has stopped, while th…

[Spcfork]

Ah, so I am halfway right.
It’s just a visual bug!

Probably shouldn’t worry,
after all, who would use the Private-Use Chars for anything printable anyway?

[Firepup650]

@Spcfork

who would use the Private-Use Chars for anything printable anyway?

Me

Context: I like the way the character looks, so I use it as an input statement. I even made it a usable part of my primary package.

[ShaneAtReplit]

Hey @CoderElijah!

Thank you for bringing this to our attention. We are working on changes to the console and its behavior, which solve this issue. We don’t have an ETA on when these changes will be out, however.