This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author erik.bray
Recipients MSeifert, Will Roberts, erik.bray, jdemeyer, mark.dickinson, rhettinger, serhiy.storchaka, smarnach
Date 2018-01-12.15:09:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Users might be better off by not seeing an unhelpful error message when passing in a numpy.int32, or they might be worse-off by having lost a cue that they were writing inefficient code (which invisibly creates temporary integer objects on every call when presumably the whole reason for using numpy was a concern for efficiency).

While it's true there are many Numpy users who don't understand what they're doing, any time they go into the Python interpreter they're losing the benefits of Numpy anyways (which are fast vectorized operations on arrays).
Date User Action Args
2018-01-12 15:09:24erik.braysetrecipients: + erik.bray, rhettinger, mark.dickinson, smarnach, serhiy.storchaka, jdemeyer, MSeifert, Will Roberts
2018-01-12 15:09:24erik.braysetmessageid: <>
2018-01-12 15:09:24erik.braylinkissue30537 messages
2018-01-12 15:09:24erik.braycreate