Type of input() is not correct for Python 3

[neilccbrown]

In Python 2 input() returned a number or string dynamically. This led to its annotation (in scopes.BuiltinNames) as returning BuiltinTypes.ANY_TYPE. In Python 3, after PEP 3111 ( https://peps.python.org/pep-3111/ ) input changed to always returning a string. Ideally I think TigerPython would dynamically alter the return type of the input function based on the Python version but I'm not sure the best way to structure this as BuiltinNames has all the functions statically determined, so it is not easy to pass in the python version during the construction.

(This is not critical for us as I think we're going to use builtins.pyi to annotate all the builtins rather than use TigerPython's set, but I thought I'd point this out.)

[Tobias-Kohn]

Thanks for pointing this out. There is a bit of historical baggage here.

TigerJython/TigerPython was originally written with Python 2 (because Jython only had support for Python 2.7), which had an awful behaviour for input(). I changed that to a more "sensible" one where the input was parsed as an integer, float or returned as a string otherwise. Because of backward compatibility with existing textbooks, we kept this behaviour in TigerPython even though it is now based on Python 3.

I think we will therefore have to add a switch in there to make it serve out differing needs.