Closed xylar closed 2 months ago
I've noticed this in CI but haven't had time to deal with it yet, especially because it seems to be related to Linux only; I can't reproduce it with macOS (M1) and Python 3.13.0rc1. I'll try on Linux soon.
https://github.com/igraph/python-igraph/commit/8abba79c19675f39e4648e9b03bcd000b965ee3c might be a fix for this issue; let's see how it fares in CI.
@ntamas, thanks for responding so quickly! Fingers crossed.
CI passed. I'm aiming for a new patch release soon(ish), in the next few days. You can apply 8abba79 manually if you can't wait for the next patch release.
@ntamas, Thanks for adding this support so quickly! I'll take your suggestion and patch for now.
Based on the attempt to build with python 3.13 on conda-forge, it seems like some work may be needed before python-igraph is compatible. We're seeing failures in a lot of tests with messages like the following:
See https://github.com/conda-forge/python-igraph-feedstock/pull/91
Also likely relevant: