We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas.
I have confirmed this bug exists on the master branch of pandas.
l0_id 3 l1_id 4 Name: 0, dtype: float64 row.at['dist', 1] --------------------------------------------------------------------------- TypeError Traceback (most recent call last) <ipython-input-601-419ac8472e13> in <module> ----> 1 row.at['dist', 1] ~/.conda/envs/lex/lib/python3.6/site-packages/pandas/core/indexing.py in __getitem__(self, key) 2198 2199 key = self._convert_key(key) -> 2200 return self.obj._get_value(*key, takeable=self._takeable) 2201 2202 def __setitem__(self, key, value): TypeError: _get_value() got multiple values for argument 'takeable' but row.set_value('dist', 1) works fine
#26989 Series with MultiIndex "at" function raises "TypeError" This error still exists .set_value works, at[] doesnt
please dont deprecate set_value until the replacement works
pandas 0.25.3
The text was updated successfully, but these errors were encountered:
row.at['dist'] = 1
Sorry, something went wrong.
No branches or pull requests
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas.
I have confirmed this bug exists on the master branch of pandas.
Reproducible Example
Issue Description
#26989 Series with MultiIndex "at" function raises "TypeError"
This error still exists
.set_value works, at[] doesnt
Expected Behavior
please dont deprecate set_value until the replacement works
Installed Versions
pandas 0.25.3
The text was updated successfully, but these errors were encountered: