Installation issue -- pandas.io has no attribute parquet about abagen

[rmarkello]

Sorry to hear this is happening! I'm not totally sure the cause, but definitely interesting in figuring out what's up. Would you mind giving me the output you get running the following code:

import pandas as pd
pd.show_versions()

That might help narrow things down a bit!

[illdopejake]

Heck yeah!

INSTALLED VERSIONS
------------------
commit: None
python: 3.6.2.final.0
python-bits: 64
OS: Linux
OS-release: 4.4.0-145-generic
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_CA.UTF-8
LOCALE: en_CA.UTF-8

pandas: 0.20.3
pytest: 3.2.2
pip: 9.0.1
setuptools: 36.4.0
Cython: None
numpy: 1.15.4
scipy: 1.1.0
xarray: None
IPython: 6.1.0
sphinx: None
patsy: 0.4.1
dateutil: 2.6.1
pytz: 2017.2
blosc: None
bottleneck: None
tables: 3.4.3
numexpr: 2.6.2
feather: None
matplotlib: 2.0.2
openpyxl: None
xlrd: 1.1.0
xlwt: None
xlsxwriter: None
lxml: None
bs4: None
html5lib: 0.999999999
sqlalchemy: None
pymysql: None
psycopg2: None
jinja2: 2.9.6
s3fs: None
pandas_gbq: None
pandas_datareader: None

[rmarkello]

Perfect!

For some reason your pandas install is a few versions old (0.20.3, where the current version is 0.24.2), and the ability to read parquet files only came about in 0.21.0, which explains the error. Could you try updating your pandas install (if you're comfortable with that) and try importing again and let me know how that goes?

In the meantime I'll update the install requirements for abagen to reflect the minimum version dependency and try and implement a few other fixes to catch these sorts of errors.

[illdopejake]

That was indeed the problem, it seems! It also didn't help that I had created the new environment with conda, so Pip and Conda packages were getting crossed up.

Creating a new environment from scratch using virtualenv did the trick!

Thanks for the rapid and super helpful response -- can't wait to get jiggy with Abagen

[rmarkello]

Great, glad that worked! I'll close this issue as soon as I merge in the changes to prevent this problem in the future 👍 Thanks for pointing it out, and let me know if you run into any other problems as you work with the package!

[rmarkello]

Alright, I think this was closed with #41. If any more issues pop up then we can address them as they're discovered!