Assignments: numerics, strings and .loc

[aldanor]

Why would assigning an entire column to an array of values work differently with numbers vs strings?

Assigning numeric values:

>>> df = pd.DataFrame(columns=['x', 'y'])
>>> df['x'] = [1, 2]
>>> df
   x    y
0  1  NaN
1  2  NaN

Assigning string values:

>>> df = pd.DataFrame(columns=['x', 'y'])
>>> df['x'] = ['1', '2']
ValueError: could not broadcast input array from shape (2) into shape (0)

Btw according to latest docs .loc can append, but can it append more than one value at once?

Setting multiple via .loc:

>>> df = pd.DataFrame(columns=['x', 'y'])
>>> df.loc[:, 'x'] = [1, 2]
>>> df
Empty DataFrame
Columns: [x, y]
Index: []
>>> df.loc[[0, 1], 'x'] = [1, 2]
>>> df
Empty DataFrame
Columns: [x, y]
Index: []
>>> df.loc[0:2, 'x'] = [1, 2]
>>> df
Empty DataFrame
Columns: [x, y]
Index: []

Setting single via .loc: (this works ofc)

>>> df = pd.DataFrame(columns=['x', 'y'])
>>> df.loc[0, 'x'] = 1
>>> df
   x    y
0  1  NaN

[jreback]

This is not valid python code (what you pasted)

>>> df = pd.DataFrame(columns='x', 'y')
SyntaxError: non-keyword arg after keyword arg

[TomAugspurger]

Presumably missing square brackets.

[aldanor]

Yea I retyped it manually, a typo.

[jreback]

can you fix the examples pls

[aldanor]

Fixed typos, should work now; sry had to type it manually.

Huh, more weird stuff, check this out:

>>> df = pd.DataFrame(columns=['x', 'y'])
>>> df.x = [1, 2]  # no error?
>>> df.y  # expect [nan, nan]?
ValueError: Wrong number of items passed 2, indices imply 0

Btw: this is v0.13.0, not the head rev; not sure if it has been addressed or not already but I skimmed through recent changes/issues and haven't found anything related.

[jreback]

assigning to columns via setattr is currently an open issue (should this actually error), hard to say, see here: #5904

[aldanor]

@jreback Still crashes with __setitem__ as well.

[jreback]

@aldanor what are you refurring to: Still crashes with __setitem__ as well.

[aldanor]

@jreback Maybe I got it wrong; did you mean df.x = ... kind of access by "assigning to columns via setattr", as opposed to df['x']? The latter behaves the same in all the above cases.

[jreback]

@aldanor pls roll the setting with multiple .loc into a new issue (ref this issue though); I am not sure what to do with them; I think they should raise actually, pushing off to 0.14 in any event

[jreback]

df.x = something works, but is just an attribute assignment, it blows up if x is a column (see the references issue) (which is guarding against assigning to a method, but same idea)

[jreback]

@aldanor FYI, I fixed the assignments to an empty frame; if you are finding bugs, great!

but I would not use this in practice as you will almost always get object dtype

so not that useful

[aldanor]

Yea I was just using the code above for cheap and dirty unit tests and was surprised to see it blows up (in many different ways). What do you mean by "always get the object dtype" though? df.x = [1, 2] would result in np.int64 wouldn't it? Does for me at least.

Thanks for the quick PR; will move the .loc stuff to another issue.