Tamás Nepusz
Tamás Nepusz
I think this question belongs to the [support forum](https://igraph.discourse.group) and not here. I guess you are following the [tutorial](https://igraph.org/c/doc/igraph-Tutorial.html#tut-lesson-1-compiling-with-cmake), and the problem is that you have forgotten to create a...
`PyErr_CheckSignals()` does not do anything when called from a non-main thread, according to the [docs](https://docs.python.org/3/c-api/exceptions.html#c.PyErr_CheckSignals): > If the function is called from a non-main thread, or under a non-main Python...
Not a direct igraph issue so closing.
#179 is fixed and so is this
Yup, but note that this is R where we _don't_ have Cairo and `matplotlib` :)
Note: in igraph 0.10 we now have `igraph_get_all_eids_between()`, which will probably solve the problem that is outlined here. We "just" need to transition the C core of the R interface...
@iosonofabio Since you guys are already working on a vignette for R-igraph, this issue might be of potential interest to you as an example of something that could be clarified...
Note to ourselves: a key problem here is that we have lots of hand-written code in the R interface that assumes that igraph's error handler will `longjmp()` -- that's why...
Given the state of `ggraph`, I think we can safely close this as there is no need to implement this in igraph itself. Feel free to reopen if needed.
Yes, the issue is still open and feel free to get started on it. There's no wiki page but the README contains some instructions for getting started with development (after...