On Sa, 2015-03-07 at 18:21 -0800, Jaime Fernández del Río wrote:
snip
I note that on SO Jaime made the suggestion that take use
unsafe casting and throw an error on out of bounds indexes.
That sounds reasonable,
On 08.03.2015 11:49, Sebastian Berg wrote:
On Sa, 2015-03-07 at 18:21 -0800, Jaime Fernández del Río wrote:
snip
I note that on SO Jaime made the suggestion that take use
unsafe casting and throw an error on out of bounds
On Sat, Mar 7, 2015 at 2:45 PM, Charles R Harris charlesr.har...@gmail.com
wrote:
On Sat, Mar 7, 2015 at 2:02 PM, Dinesh Vadhia dineshbvad...@hotmail.com
wrote:
This was originally posted on SO (
https://stackoverflow.com/questions/28853740/numpy-array-casting-ruled-not-safe)
and it was
On Sat, Mar 7, 2015 at 2:02 PM, Dinesh Vadhia dineshbvad...@hotmail.com
wrote:
This was originally posted on SO (
https://stackoverflow.com/questions/28853740/numpy-array-casting-ruled-not-safe)
and it was suggested it is probably a bug in numpy.take.
Python 2.7.8 |Anaconda 2.1.0 (32-bit)|
On Sat, Mar 7, 2015 at 1:52 PM, Charles R Harris charlesr.har...@gmail.com
wrote:
On Sat, Mar 7, 2015 at 2:45 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Sat, Mar 7, 2015 at 2:02 PM, Dinesh Vadhia dineshbvad...@hotmail.com
wrote:
This was originally posted on SO (
