> I'm not looking to call python libs from julia. I have a large investment > in python code. The obvious (to me) path to try out some julia is to move > a > function or 2 into julia, and be able to call julia from my python main > program. So I would need a working pyjulia to do this.
Yes, my PyCall.jl, suggestion, was probably not to helpful.. While you can use it to call TO Julia, using callbacks I guess, I assume you would be reimplementing pyjulia on your own from scratch.. Calling from Python, for sure worked at some point even recursively (might not be well tested, even less that only pyjulia) back and forth: Julia Calling Python Calling Julia... http://blog.leahhanson.us/post/julia/julia-calling-python.html Now, I'm not sure what changed, at least Julia 0.4 came along and something broke pyjulia. You could help or wait for it to get fixed. OR if you are just trying out, you could use what did work. I think that would then be Julia 0.3.12: A. http://julialang.org/downloads/oldreleases.html Is it preferred. No, but ok, to start out trying Julia.. 0.4 sure got better, e.g. faster/incremental GC, but Julia sure was fast in 0.3, and even 0.2. These major version upgrades DID break some syntax (why they are major versions). Some are trivial changes, such as case of integer types. It would get annoying having to change but not you can use the newer syntax using Compat.jl. And you do not have to actually specify the type that often (never for speed). B. Another option is https://github.com/wavexx/Polyglot.jl PyCall or pyjulia would almost always be preferred to that, except when it's not :) e.g. say running on different machines, or when, say either, e.g. the latter pyjulia doesn't work. This is still a neat project (at least for other languages), that I haven't tried. Hopefully 0.4 didn't break it.. -- Palli.
