4 Apr
2016
4 Apr
'16
10:23 p.m.
I'm on NumPy 1.10.4 (mkl).
np.uint(3) // 2 # 1.0 3 // 2 # 1
Is this behavior expected? It's certainly not desired from my perspective. If this is not a bug, could someone explain the rationale to me. Thanks.
2926
Age (days ago)
2936
Last active (days ago)
9 comments
7 participants
participants (7)
-
Antoine Pitrou -
Antony Lee -
Charles R Harris -
Eric Firing -
Nathaniel Smith -
Robert Kern -
T J