You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm unable to use tuples as index keys in the newest version 0.23.4 like I was able to in 0.22.0. I have some software that is dependent on this functionality. Is there any way to add this functionality back into the coming versions?
Expected Output
I was expecting to be able to create a pd.Series object from my param_index dictionary object.
I ended up doing this a quick fix for version stability. I wasn't sure what the problem was at first from the error message. I ended up doing this which is compatible with both versions:
Code Sample, a copy-pastable example if possible
I've posted this bug on issue 15457 and the issue was closed but it still occurs in the current version (0.23.4)
Problem description
I'm unable to use tuples as index keys in the newest version
0.23.4
like I was able to in0.22.0
. I have some software that is dependent on this functionality. Is there any way to add this functionality back into the coming versions?Expected Output
I was expecting to be able to create a
pd.Series
object from myparam_index
dictionary object.Output of
pd.show_versions()
INSTALLED VERSIONS
commit: None
python: 3.6.4.final.0
python-bits: 64
OS: Darwin
OS-release: 15.6.0
machine: x86_64
processor: i386
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8
LOCALE: en_US.UTF-8
pandas: 0.23.4
pytest: 3.4.0
pip: 9.0.1
setuptools: 39.0.1
Cython: 0.27.3
numpy: 1.14.3
scipy: 1.0.0
pyarrow: 0.8.0
xarray: 0.10.3
IPython: 6.4.0
sphinx: 1.7.4
patsy: 0.5.0
dateutil: 2.6.1
pytz: 2018.3
blosc: None
bottleneck: None
tables: None
numexpr: None
feather: 0.4.0
matplotlib: 2.2.2
openpyxl: 2.5.0
xlrd: 1.1.0
xlwt: None
xlsxwriter: None
lxml: None
bs4: 4.6.0
html5lib: 1.0.1
sqlalchemy: None
pymysql: None
psycopg2: None
jinja2: 2.10
s3fs: None
fastparquet: None
pandas_gbq: None
pandas_datareader: None
The text was updated successfully, but these errors were encountered: