Closed zacps closed 1 year ago
@zacps I can't reproduce this. Can you share more information about your environment?
What operating system are you using? What version of python are you using? Are you using a virtualenv? Do you have any other packages installed?
@LilyFoote It seems like the issue only occurs when pandas is installed as well, minimal reproduction:
FROM ubuntu:22.04
RUN apt update && \
apt install -y \
python3 \
python3-pip
RUN pip install \
kolo==2.11.0 \
numpy==1.24.3 \
pandas==2.0.2
COPY <<EOF repro.py
import numpy
print("Succeeded")
EOF
ENTRYPOINT [ "kolo" ]
CMD ["run", "repro.py"]
docker build -t kolo-repro . && docker run kolo-repro
@zacps I did manage to replicate this with numpy 1.24.3 and 1.24.4. Installing 1.25.0 fixed it for me. I tried bisecting numpy and found https://github.com/seberg/numpy/commit/60a858a372b14b73547baacf4a472eccfade1073, but I don't see why that would be relevant.
Neither do I. I think my first inclination would be to attach a debugger and step through to see exactly where that traceback comes from. I'm not sure I believe it, certainly the pyx
frames don't have sensible line numbers at the very least.
Unfortunately that's probably past what I can justifiably do on the clock!
I've tracked down the bug and I'll release the fix today. Thanks for the report!
Running without kolo works as expected.