-
Notifications
You must be signed in to change notification settings - Fork 10
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
Qurro will break on newer (>= 2020.11) versions of QIIME 2 #315
Comments
A specific source of difficulties :
It 'fixes' that error, but it is unclear how this may break other feautures / functionality of qiime2. |
Any updates on this ticket? Just ran into this problem running the latest version of QIIME2. Also noticed the altair version is pinned at exactly |
Sorry, I don't have an update on this yet. The pandas (and altair) updates
are both definitely surmountable, but these changes -- mostly the altair
one -- will involve changing an uncomfortably large amount of the codebase.
The pandas issue is probably easier to fix since it only impacts the Python
side of things. However, the altair pin is (IIRC) due to mismatches with
the Vega-Lite version used by newer versions of altair (
#216), so even if we update it on
the Python side we'll need to make sure that everything on the JS side
works properly. This is doable! However, I'm very hesitant to risk breaking
things, especially since I haven't touched this codebase in a while.
For now, the shoddy workaround solution is installing an older version of
QIIME 2 (2020.8 should be the latest version that works, due to the pandas
version used) and then installing Qurro into that QIIME 2 environment.
However, I recognize this is not ideal, and if time permits I'd like to fix
this situation. Sorry for the trouble; PRs are welcome in case anyone wants
to take a crack at this.
…On Mon, Apr 4, 2022 at 10:48 AM Yoshiki Vázquez Baeza < ***@***.***> wrote:
Any updates on this ticket? Just ran into this problem running the latest
version of QIIME2. Also noticed the altair version is pinned at exactly
3.1.0 which is almost 3 years old, it would be nice if the version
requirements were a little more forgiving.
—
Reply to this email directly, view it on GitHub
<#315 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA736P5HMAAHKI2IONJLZWTVDMTNXANCNFSM4UXAR7WA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Thanks for the update! 😵 |
See biocore#258 and biocore#315. not confident this is done yet (and if nothing else the rest of the code gleefully refers to "SparseDataFrame" because 2019 marcus was a schmuck), but this at least fixes a fair amount of failing tests
…QIIME 2 (#322) * DEP: Update setup.py re: python and pandas #315 * DEV: port CI from Travis to GH Actions: close #316 * TST: For now, omit "make notebooks" from CI Maybe we can make another GitHub Actions for these later; but Songbird is causing tensorflow nonsense to pop up, and this is not the sort of thing I think we should spend time fixing (esp with the advent of birdman) * DEP: pin min biom vsn and add some comments * DEP: Fix biom_table_to_sparse_df for pandas >= 1 See #258 and #315. not confident this is done yet (and if nothing else the rest of the code gleefully refers to "SparseDataFrame" because 2019 marcus was a schmuck), but this at least fixes a fair amount of failing tests * DEP: remove some warnings, docs, fix a test re: pd * TST: Fix the python tests!!! #258 The problem was using .loc[] on these sparse dataframes. whoops * STY: tiny style fixes * DEP: knock out some pandas warnings * DEP: np.matrix() -> np.array() in qarcoal tests since apparently it's deprecated, or about to be deprecated, idk * DEP/STY: Fix more warnings; remove unused import most of these warnings were just pd.DataFrame.append() being deprecated and replaced with pd.concat() * DOC: one of the demos' JS data slightly changed looks like it's a tiny floating-point thing -- probably an artifact of working here on a new operating system, on a new python version, a new pandas version, a new biom version, etc. shouldn't make a noticeable difference * DOC: update readme re: min Q2 vsn * TST: matrix of qiime 2 versions nice! * TST: more detailed comment about Q2 vsn matrix * DOC: remove the "Sparse" from "SparseDataFrame" * REL: version kick * TST: Add standalone CI IIRC something about how our specific altair version works makes it incompatible with python 3.10. let's test that here -- if needed, we can update the README to disallow python versions >= 3.10. (And then we can look into removing the altair pin when absolutely needed.) * TST: attempt to get standalone tests working * TST: attempt to fix pytest q2 exclusion * DEP: ok py 3.10 is a no go * STY: fix formatting * DOC: Rerun 4 / 6 example notebooks Songbird and ALDEx2 ones will cause problems * DOC: tidy/update readme refs * DOC: update jake fish dataset ref on website * DOC: Fix songbird notebook!, standardize output rm * BLD: rm (now-)unused comments from q2 ci * DOC: fix transcriptomics ntbk :) * REL: update changelog * REL: update changelog * TST: see if we can finagle q2 2020.6 / 2020.8? since i thiiiink these versions mighta worked with the pandas >= 1 syntax that being said, i don't think it makes sense to devote time/energy to officially supporting them; just wanna check * TST: remove Q2 2020.6 / 2020.8 in CI Looks like the tests themselves pass for these versions, but the style-checking with black fails due to incompatibility with click. yeah this is enough for me to not bother supporting these versions imo * DOC: songbird compatibility deets * DEV/DOC: update dev docs re: 2022 the apocalypse came and all i got was this pull request * REL: update changelog about updating contributing about about about about aboot * REL: minor chglog tidying
I apologize for the long delay in fixing this. Qurro v0.8.0 is now available on PyPI (the conda-forge version should be automatically updated soon), and supports all versions of QIIME 2 ≥ 2020.11. |
Due to #258 -- ideally we will need to cut a new release that uses pandas 1, and clearly document which version to install based on the version of QIIME 2 in use.
For now, a faster solution would be just clearly documenting somewhere that Qurro, for now, can't work with QIIME 2 2020.11 and future versions, due to the pandas thing.
The text was updated successfully, but these errors were encountered: