Add warning message when using input with eval command

[Ibrahim2750mi]

Closes #2420
Closes (MAYBE) #2255

We could check if EOFError is in the result (as well as maybe checking that "input" is on their code and the status code indicated an error), and if so add a message after the codeblock saying that input doesn't work with the bot.

No need to check if input is in their code as the docs say EOFError is only raised when

the input() function hits an end-of-file condition (EOF) without reading any data

Screenshots:

[Ibrahim2750mi]

Also wookie thanks for reviewing

[mbaruh]

A false positive here would be

!e raise ValueError("EOFError: EOF when reading a line")

Not sure this is worth handling though. If you tried to find input in the eval input you would also have a false positive in the form of someone shadowing the built-in, as beginners often do.

[Ibrahim2750mi]

A false positive here would be

!e raise ValueError("EOFError: EOF when reading a line")

I also realised this and commented it in the first review there wookie recommended to leave this as no user would do this.

Not sure this is worth handling though. If you tried to find input in the eval input you would also have a false positive in the form of someone shadowing the built-in, as beginners often do.

Just doing if "input" in code: is a grave mistake same goes with raise. If we check that there is input or raise in the code we need to do it with ast and not comparing it just with string.

[Robin5605]

Sort of along the same lines as #2255 , how feasible would it be to add a modal with a TextInput that will be fed into input()?

[Ibrahim2750mi]

Sort of along the same lines as #2255 , how feasible would it be to add a modal with a TextInput that will be fed into input()?

I don't get whats the use of adding any input, eval command is not there to build an user interface. Any use of user input can be hard coded.

[wookie184]

Works nicely, thanks!