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 going to suggest a workaround in matplotlib for the moment. Changing type in this use case shouldn't be a big issue, it only happens once for each animation created.
LB, an exception is a graceful shutdown, not a crash. A crash is a seg fault, core dump, or an OS message 'Your app has stopped unexpectedly'.
In bpo-30537, the exception was regarded as expected, not a bug, and changing islice to accept np ints was regarded as an enhancement, and therefore limited to 3.7
Activity
braaannigan commentedon Aug 1, 2017
The error arises when this code is used:
itertools.islice( [3, 4, 5], np.int64(2) )
but not with this
itertools.islice([3,4,5], 2)
rhettinger commentedon Aug 1, 2017
See http://bugs.python.org/issue30537
braaannigan commentedon Aug 1, 2017
Thanks Ray. The use case is here:
https://stackoverflow.com/questions/45356718/saving-matplotlib-animation-leads-to-error/45438057#45438057
I'm going to suggest a workaround in matplotlib for the moment. Changing type in this use case shouldn't be a big issue, it only happens once for each animation created.
mdickinson commentedon Aug 1, 2017
That actually looks as though it may be worth a bug report to the matplotlib folks.
braaannigan commentedon Aug 1, 2017
Hi Mark - I've done that here:
matplotlib/matplotlib#8973
Liam
terryjreedy commentedon Aug 5, 2017
LB, an exception is a graceful shutdown, not a crash. A crash is a seg fault, core dump, or an OS message 'Your app has stopped unexpectedly'.
In bpo-30537, the exception was regarded as expected, not a bug, and changing islice to accept np ints was regarded as an enhancement, and therefore limited to 3.7