RetroSearch Browse

Fri Sep 2 21:18:34 EDT 2016 · https://mail.python.org/pipermail/python-dev/2016-September/146098.html

Chris Angelico wrote:
> Forcing people to write 1.0 just to be compatible with 1.5 will cause
> a lot of annoyance.

Indeed, this would be unacceptable IMO.

The checker could have a type 'smallint' that it
considers promotable to float. But that wouldn't
avoid the problem entirely, because e.g. adding
two smallints doesn't necessarily give a smallint.

Seems to me the practical thing is just to always
allow ints to be promoted to floats. It's possible
for runtime errors to result, but this is Python,
so we're used to those.

-- 
Greg

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2016-September/146098.html below:

[Python-Dev] What should a good type checker do? (was: Please reject or postpone PEP 526)