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
I'm not sure whether this is a problem with PyPydatetime.py, or future or something else, but it got me to thinking. What if isinstance(newint(x), int) evaluated to True iff x <= sys.maxint and x >= (-sys.maxint - 1)? Would that be absurd or break things? It is, after all, called int, but behaves exclusively like a long with respect to the above context in Python 2.
The text was updated successfully, but these errors were encountered:
Consider the following on PyPy (which uses a pure python version of
datetime
):This, of course, can be worked around using:
This does not happen on cPython, which uses a C implementation of
datetime
:I'm not sure whether this is a problem with
PyPydatetime.py
, orfuture
or something else, but it got me to thinking. What ifisinstance(newint(x), int)
evaluated toTrue
iffx <= sys.maxint and x >= (-sys.maxint - 1)
? Would that be absurd or break things? It is, after all, calledint
, but behaves exclusively like along
with respect to the above context in Python 2.The text was updated successfully, but these errors were encountered: