-
Notifications
You must be signed in to change notification settings - Fork 7
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
Incompatibility of pybiomart
and omnipath
#54
Comments
Hi Pau, I think it has nothing to do with the sqlite file (that would be indeed surprising), the most likely I can think about is
Already import time Also, this seems to be a
I'm not familiar with
Note, the -196, -196 is because at this point I've already tinkered with this file, originally it was a double read error, with 392 read, -196 more expected. We have no chance to work around this issue in Btw,
|
Wow @deeenes! You seems to have solved this mystery, after installing your |
@PauBadiaM I released @deeenes's fix in the latest version of requests-cache. I see pybiomart doesn't pin any of its dependencies, so you can pin requests-cache in your own project if you'd like, i.e. |
Hi @deeenes, there seems to be a weird bug regarding
pybiomart
andomnipath
. In the beginning of the pseudobulk vignette ofdecoupler
I usepybiomart
to retrieve gene symbols and then later I import collectri. The problem is that when I run the gene symbol query, it generates a hidden file called.pybiomart.sqlite
which triggers a huge amount of warnings foromnipath
. This used to not be the case since you can pass the argumentuse_cache=False
but it still creates the file anyways now, I've opened an issue about it scverse/scanpy#2861I tried deleting the file before loading collectri but
omnipath
still spams warnings and falls to the static tables. The only way to make it work is to load first collectri and then biomart, which breaks the flow of the vignette. Is there anything that can be done fromomnipath
to solve this? Any clue what might be causing it?You can reproduce the error by running:
Thanks!
The text was updated successfully, but these errors were encountered: