You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Python 3, future.builtins.int == int, and pow operates as expected.
In Python 2, future.builtins.int == newint and the 3-argument version of pow fails.
The 2-argument version works fine; it seems that in Python 2, the 2-argument version will take any int-like argument, but the 3-argument version will only take int:
In Python 3,
future.builtins.int == int
, andpow
operates as expected.In Python 2,
future.builtins.int == newint
and the 3-argument version ofpow
fails.The 2-argument version works fine; it seems that in Python 2, the 2-argument version will take any
int
-like argument, but the 3-argument version will only takeint
:Looking at the source,
future.builtins.pow
uses the Python 2pow
transparently, when it should be handling the presence ofnewint
s.The text was updated successfully, but these errors were encountered: