Closed peterjc closed 6 years ago
(I'm not sure which of the various bits of PacBio package stack the minimum version of numpy needs to be declared, presumably only those which have compiled Python code using the NumPy C API)
We are looking into it and will come back to you.
Thank you all, that was quick.
oh and one final thing: It was correct that you submitted it here, please let us deal with the meta.yaml
files in the bioconda repo (otherwise we also lose the mental overview of changes to our recipes).
I'm unclear if this should reported here, or on the BioConda repository (where I could submit a pull request to update the
meta.yaml
file).Operating system Linux
Package name Which package / tool is causing the problem? Which version are you using, use
tool --version
. Have you updated to the latest versionconda update package
?Using
genomicconsensus-2.3.2
(latest version), bug shown withvariantCaller --version
as described below.Describe the bug A clear and concise description of what the bug is.
API incompatibility warning with
genomicconsensus-2.3.2
andnumpy-1.15.1
Error message Paste the error message / stack.
To Reproduce Steps to reproduce the behavior. Providing a minimal test dataset on which we can reproduce the behavior will generally lead to quicker turnaround time!
Then,
Updating numpy fixed this,
Expected behavior A clear and concise description of what you expected to happen.
The dependencies Arrow (etc) should ensure a version of NumPy compatible with what was used to compile the binaries gets installed on conda.
From trying
$ conda install numpy==1.14
which also works, it seems we need at least numpy 1.14 in the recipe'smeta.yaml