Closed callum-b closed 1 year ago
Hi @callum-b,
I met the same problem. I think there is something wrong with the latest version. I tried to install an earlier version(0.3.18), and it works for me.
Best, Xuan
Thanks for the reply @XuanrZhang ! I tried that but then I get a numpy error about np.float being deprecated. What version of numpy do you have? And did you install just pyBigWig 0.3.18, or did you get a whole different DeepTools release?
Thanks for the reply @XuanrZhang ! I tried that but then I get a numpy error about np.float being deprecated. What version of numpy do you have? And did you install just pyBigWig 0.3.18, or did you get a whole different DeepTools release?
Hi Cal, my numpy version is 1.23.5. I just installed pyBigWig not the whole Deeptools release.
Thanks for letting me know. This switch to using wheels is a real pain. If you're using this for deepTools, is there a reason you're installing that with pip rather than conda? The latter is generally preferred for all packages.
@dpryan79 personally, I'm just not a big conda user and am not familiar with it enough to use for most stuff. However, while looking at workarounds for this issue, I also looked at installing DeepTools and/or pyBigWig using conda, also to no avail. But seeing as I'm not intimate with that system and explored the pip install issue more, I kept my issue constrained to just this.
conda create -n deeptools_3.5.1 -c conda-forge -c bioconda deeptools=3.5.1
will give you a clean environment with deeptools, pyBigWig and all other dependencies. I'll look into the issue you reported though, since that's going to bite a number of people :(
I've made the first baby step and determined why it's not finding the module. The .so file in the wheel has a "37m" in the name since it is built automatically under python 3.7. Apparently that needs to be changed since that string needs to match the python version used on the installation side...which will very rarely be python 3.7 at the moment. I just need to figure out how to change this to use manylinux instead.
Fingers crossed that this is fixed in 0.3.22
A quick test with python 3.11 suggests that this is now working properly. Please comment and reopen the issue if this is still not working on your end!
On two different machines (one Ubuntu, one Debian), I can't install pyBigWig through pip. Pip thinks it's isntalled, but the module can't be imported in Python (tried in 3.8.10 and 3.11.2). Installing deeptools directly also doesn't bring pyBigWig along with it.
There is also no "pyBigWig" directory in
.local/lib/python3.8/site-packages/
, whereas most of my python packages do have that.The latest release on the pypi page is listed as 31/03/2023, so perhaps something went wrong there.