-
Notifications
You must be signed in to change notification settings - Fork 616
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
ValueError with sc.pp.highly_variable_genes with pandas 0.24 #450
Comments
I have also got the same problem. And I have fixed the issue by reinstalling pandas to 0.23 |
Same problem here. So glad that I found this ticket. From flying-sheep's commit, it looks like either upgrading scanpy to the newest version or downgrading pandas would work. There is also some anndata version requirement going up, no idea why. |
because part of the fix is in anndata, of course! |
Thank you so much for fixing this, @flying-sheep! |
Sure! @ivirshup figured out independently within 2 hours of me that The fix needed three parts:
|
Dear All, I get a similar error than above:
These the packages I have installed for this analysis both conda and pip |
Hi @helios, You will have to install scanpy from github to use the fix for this. The latest release (1.3.7) does not yet include the fix. |
Hi @LuckyMD, |
@flying-sheep, so, we need 1.3.8 essentially, now, right? |
Yes. Do you think scanpy is quality-controlled enough that we can cut new releases whenever we please? Else I’m not comfortable to just create a new tag from master and release it by myself. |
Good, yes, in the meanwhile, test coverage should be high enough. I can't think of any major hole anymore. Still, it would be nice to briefly coordinate for Scanpy; at least, still these days. But yes, in this case, please make release 1.3.8! |
I did, and then I realized that we have the |
Wasn't entirely planned to have 1.4 exactly now, but, fine, we have some stuff already 😄 I briefly tweeted about it: https://twitter.com/falexwolf/status/1093140419997822978 |
Minimal example:
Output:
The error is gone with pandas 0.23.4. There was a change in the API of reindex in pandas: http://pandas.pydata.org/pandas-docs/stable/whatsnew/v0.24.0.html
The text was updated successfully, but these errors were encountered: