Closed HaraldWilhelmi closed 2 years ago
Uninstalling numpy 1.16.6 before did not help.
Also upgrading numpy is not an option:
$ pip install --upgrade numpy
Requirement already satisfied: numpy in /beegfs/biosw/circtools/1.2.1/venv/lib/python3.9/site-packages (1.16.6)
Collecting numpy
Using cached numpy-1.22.3-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (16.8 MB)
Installing collected packages: numpy
Attempting uninstall: numpy
Found existing installation: numpy 1.16.6
Uninstalling numpy-1.16.6:
Successfully uninstalled numpy-1.16.6
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
circtools 1.2.0 requires biopython>=1.71, which is not installed.
circtools 1.2.0 requires pandas>=0.25.0, which is not installed.
circtools 1.2.0 requires reportlab>=3.3.0, which is not installed.
circtools 1.2.0 requires scipy>=0.19.0, which is not installed.
circtools 1.2.0 requires statsmodels>=0.9.0, which is not installed.
fuchs 0.3.0 requires numpy<1.17.0, but you have numpy 1.22.3 which is incompatible.
Successfully installed numpy-1.22.3
Actually I diverted in two points from the official instructions:
Using the default pip and running without wheel made no difference.
After looking closer at the stack backtrace and comparing my setup with an older installation, I decided to to try that as a workaround:
pip install HTSeq==0.13.5
That looks promising but I have to compile from scratch to be certain.
Suggested workaround works. What would be a good final fix? The requirement for the old numpy version seems to come from FUCHS. Modernizing here might be the most consequent solution. Integrating the workaround into the installation processes of circtools may be cheaper however.
Hi Harald,I went through my notes for FUCHS and I don't think there is a reason we need to keep numpy locked for FUCHS. I'll commit a change to the FUCHS repository to use the latest numpy which in turn should also fix the DCC error.
Forgot about this bug (and was happy with my workaround). After installing circtools again, I noticed that I no longer need the workaround. So this issue is most certainly resolved.
When installing the circtools in a Python3 venv, I got a inconsistent numpy setup. That can be seen with that example:
./venv/bin/circtools detect
Expected behavior:
Actual behavior:
Some addition facts:
Also I did already some research: