Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
ValueError: buffer source array is read-only #11502
Comments
|
yep looks like the same issue why do you have the read only flag set in the first place? |
kyleabeauchamp
commented
Nov 1, 2015
|
I have no idea. I have a pipeline of like 20 munging steps, but I haven't actually debugged why things end up read-only. Presumably, the issue is related to the usual "copy versus view" slicing stuff that always trips people up. |
jreback
added Enhancement Compat
labels
Nov 1, 2015
jreback
added this to the
Next Major Release
milestone
Nov 1, 2015
jreback
added Difficulty Intermediate Effort Medium
labels
Nov 1, 2015
|
@kyleabeauchamp ok. would love to see a pull-request to fix (along the same lines as the issue you mentioned above). should be straightforward to do. |
|
This error appears in 0.17.1 and 0.17.0 when trying to aggregate large tables. This error does not appear in 0.16.2. Something broke between 0.16.2 and 0.17.0. |
EvanZ
commented
Dec 18, 2015
|
Glad I stumbled upon this issue. I am running into issue training a pipeline in sklearn, and found this error "ValueError: buffer source array is read-only". It seems to only occur under sklearn 0.17.0. When I downgrade to 0.15.2 (the version I was using when I built the pipeline originally), the issue doesn't occur. I assume it's related to whatever this bug is. |
|
+1 |
This was referenced Jan 6, 2016
jreback
modified the milestone: 0.18.0, Next Major Release
Jan 13, 2016
|
closed by #12033 |
kyleabeauchamp commentedNov 1, 2015
After upgrading to 0.17 (anaconda 2.7 + OSX), I'm finding that some previously working code is failing with
ValueError: buffer source array is read-only. Driver code is below. The issue is basically the series version of #10043. I think the problem is that the patch for #10043 (#10070) only fixed thetake_2dtemplates, leaving thetake_1d(Series) versions with the old behavior. Based on my naive understanding, it might be straightforward to extend #10070 for the 1D cases.Stacktrace is below.