Alex Gaynor added the comment:

I can't say that I've ever used // on floats, but it seems to me anyone doing 
so (as opposed to normal division + explicit rounding) *intentionally* might be 
broken by this change, but anyone doing this incidentally is not really in a 
"gotcha" situation. Since this is a type-specific behavior, and not a 
value-specific one, I don't really think there's a win in changing the 
behavior, and staying backwards compatible is much better.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue22444>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to