Thanks for your answer, Yichao! I am installing the nightly version of julia and I will try the master version of PyCall.
I was trying to wrap C++-Igraph into my julia code by using Cpp.jl, however it seems to be a bit tricky because my c++ codes are not that simple. Do you (or anybody else) recomend another way to wrap c++ code into julia? I took a look at Cxx.jl and it seems to be more intuitive to use, but I didn't try it yet. Best, Charles On 11 July 2015 at 00:39, Yichao Yu <[email protected]> wrote: > On Fri, Jul 10, 2015 at 6:07 PM, Charles Novaes de Santana > <[email protected]> wrote: > > Dear Julians, > > > > Igraph is an amazing library to work with graphs, currently available > for R, > > C/C++ and Python (http://igraph.org). I am trying to use it with Julia > by > > using PyCall but I am facing some issues very similar to the ones > related in > > the following links: > > > > https://github.com/JuliaLang/pyjulia/issues/32 > > > > https://github.com/stevengj/PyCall.jl/issues/95 > > > > https://github.com/stevengj/PyCall.jl/issues/96 > > > > I just tried to run the following commands: > > > > julia> using PyCall > > > > julia> @pyimport igraph > > > > And got the following error: > > > > signal (11): Segmentation fault > > PyType_Ready at /usr/lib/x86_64-linux-gnu/libpython2.7.so (unknown line) > > call at /home/cdesantana/.julia/v0.4/PyCall/src/pytype.jl:73 > > pyjlwrap_type at /home/cdesantana/.julia/v0.4/PyCall/src/pytype.jl:415 > > pyinitialize at /home/cdesantana/.julia/v0.4/PyCall/src/pyinit.jl:289 > > jlcall_pyinitialize_42896 at (unknown line) > > jl_apply_generic at > > /home/cdesantana/Downloads/julia/usr/bin/../lib/libjulia.so (unknown > line) > > pyinitialize at /home/cdesantana/.julia/v0.4/PyCall/src/pyinit.jl:329 > > jlcall_pyinitialize_42814 at (unknown line) > > jl_apply_generic at > > /home/cdesantana/Downloads/julia/usr/bin/../lib/libjulia.so (unknown > line) > > pyimport at /home/cdesantana/.julia/v0.4/PyCall/src/PyCall.jl:111 > > jl_apply_generic at > > /home/cdesantana/Downloads/julia/usr/bin/../lib/libjulia.so (unknown > line) > > unknown function (ip: -775406212) > > unknown function (ip: -775409006) > > unknown function (ip: -775406239) > > unknown function (ip: -775409006) > > unknown function (ip: -775409505) > > unknown function (ip: -775404607) > > unknown function (ip: -775403490) > > unknown function (ip: -775333218) > > jl_toplevel_eval_in at > > /home/cdesantana/Downloads/julia/usr/bin/../lib/libjulia.so (unknown > line) > > eval_user_input at REPL.jl:54 > > jlcall_eval_user_input_42620 at (unknown line) > > jl_apply_generic at > > /home/cdesantana/Downloads/julia/usr/bin/../lib/libjulia.so (unknown > line) > > anonymous at task.jl:83 > > unknown function (ip: -775379519) > > unknown function (ip: 0) > > Segmentation fault (core dumped) > > > > I am running Julia version 0.4.0-dev+3735 (2015-03-09). I just installed > > FWIW, this is a REALLY old 0.4-dev version. There's been various bug > fixes after that and you'll probably have more luck with a more recent > version. > > > PyCall by calling "Pkg.add("PyCall"). I have installed python-igraph > version > > 0.6.5-1. > > Note that the latest release of PyCall might not work with current > master, You might need a checkout (master) version of PyCall. > > > > > Any clue? I am seriously thinking about wrapping Igraph for C/C++ into my > > julia code. Do you think it can be more stable? > > Depending on how simple that interface is, that might be a good idea. > And I think that's a better way in the long term. > > > > > Thanks for any help! > > > > Best, > > > > Charles > > -- > > Um axé! :) > > > > -- > > Charles Novaes de Santana, PhD > > http://www.imedea.uib-csic.es/~charles > -- Um axé! :) -- Charles Novaes de Santana, PhD http://www.imedea.uib-csic.es/~charles
