-
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
Support pandas v1: Switch from SparseDataFrame to "regular ... DataFrame with sparse values" #258
Labels
external
issues/bugs with other libraries, frameworks, etc.; might include reproducing an issue minimally
good first issue
Good for newcomers
important
Things that are critical for getting Qurro in a working/useful state
optimization
Making code faster or cleaner
Comments
fedarko
added
administrative
Logistical matters that don't have much or anything to do with code
backburner
Low-priority things that are still good to keep track of
labels
Dec 18, 2019
fedarko
added
external
issues/bugs with other libraries, frameworks, etc.; might include reproducing an issue minimally
optimization
Making code faster or cleaner
and removed
administrative
Logistical matters that don't have much or anything to do with code
backburner
Low-priority things that are still good to keep track of
labels
Dec 18, 2019
issue labels somehow got messed up, huh |
This was referenced Feb 16, 2020
fedarko
added
the
important
Things that are critical for getting Qurro in a working/useful state
label
Feb 21, 2020
Upgrading to important, since we need to get this done for the next pandas release: biocore/songbird#117 |
I don't think it is a songbird problem, but rather a problem with biom
biocore/biom-format#837
…On Fri, Feb 21, 2020, 6:04 PM Marcus Fedarko ***@***.***> wrote:
Upgrading to important, since we need to get this done for the next pandas
release: biocore/songbird#117
<biocore/songbird#117>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#258?email_source=notifications&email_token=AA75VXPUSGYASEAUNTKYRCTREBMZHA5CNFSM4J4D6VR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMUMFOY#issuecomment-589873851>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA75VXNWP7UJTSEIFGBCL4TREBMZHANCNFSM4J4D6VRQ>
.
|
If at all possible, it would be worthwhile considering using the Table
API from biom.
Thanks!
Yoshiki
…On (Feb-21-20|15:04), Marcus Fedarko wrote:
Upgrading to important, since we need to get this done for the next pandas release: biocore/songbird#117
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#258 (comment)
|
fedarko
added a commit
to fedarko/qurro
that referenced
this issue
Feb 29, 2020
fedarko
changed the title
Switch from SparseDataFrame to "regular ... DataFrame with sparse values"
Support pandas v1: Switch from SparseDataFrame to "regular ... DataFrame with sparse values"
Sep 8, 2020
fedarko
added a commit
to fedarko/qurro
that referenced
this issue
Jul 5, 2022
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
fedarko
added a commit
to fedarko/qurro
that referenced
this issue
Jul 5, 2022
The problem was using .loc[] on these sparse dataframes. whoops
2 tasks
fedarko
added a commit
that referenced
this issue
Oct 20, 2022
…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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
external
issues/bugs with other libraries, frameworks, etc.; might include reproducing an issue minimally
good first issue
Good for newcomers
important
Things that are critical for getting Qurro in a working/useful state
optimization
Making code faster or cleaner
See https://pandas.pydata.org/pandas-docs/stable/user_guide/sparse.html#migrating. For the time being it looks like running Qurro gives us a bunch of warning messages repeating this, so ... if we can avoid this that'd make the UX a lot nicer.
Addressing this might actually not be that much of a pain -- seems like the only place Sparse structures are explicitly used is in
biom_table_to_sparse_df()
, and the remainder of references to it are in comments/etc. --The text was updated successfully, but these errors were encountered: