-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
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
Pandas versions should be pinned to be below v1 #117
Comments
This might not work well with newer versions of QIIME2 since the move to 1.0 is happening (as far as I can tell) as of the next version. |
Agree @ElDeveloper , we will need a better solution for that. Not clear to me where the dep issue arise from (other than the one spotted in biom). Will need to dig into this. |
Oh dang, in the February 2020 release? I think that might break a few third-party plugins -- I know Qurro at least will also explode. @mortonjt I think the problem is due to the use of SparseDataFrame / SparseSeries rather than the new-style pandas sparse data structures -- this is why Qurro will explode on pandas 1, and an error about SparseSeries was what broke Songbird on barnacle for @vjcantu and I today |
Not a good long-term solution, but will temporarily save people from running into the problem discussed in biocore#117.
This is causing problems with the standalone songbird installation instructions. Easiest solution is just modifying this part of the README to specify the pandas version, ideal solution is modifying the setup.py/conda requirements/conda-forge dependencies to enforce this.
The text was updated successfully, but these errors were encountered: