I like to say that you are really lucky as you have the chance to built most of this things directlyinto the language itself which is a real plus, and you will most likely comme up with much betterabstraction than we do in IPython for some things.
The highlighting is off but can be fixed more easily on nbviewer than in live notebookas it is done in server side with pygments and there is already a julia theme for pygment.
But, we need to find a way to tag julia notebook so that nbviewer know the highlight to use.
On Wednesday, August 7, 2013 4:08:13 AM UTC-4, Matthias Bussonnier wrote:I like to say that you are really lucky as you have the chance to built most of this things directlyinto the language itself which is a real plus, and you will most likely comme up with much betterabstraction than we do in IPython for some things.
Yes, it is a big advantage to be doing this in the early stages of Julia, so that if the language or standard library has a problem we can just change it.
The highlighting is off but can be fixed more easily on nbviewer than in live notebookas it is done in server side with pygments and there is already a julia theme for pygment.But, we need to find a way to tag julia notebook so that nbviewer know the highlight to use.
I agree; in later IPython versions we should add some kind of metadata to the notebook to indicate the kernel etc. that it goes with.
It would be very helpful if someone who was involved in writing the Julia mode for various editors could work on the syntax highlighting etc. in IJulia:
https://github.com/JuliaLang/IJulia.jl/issues/17
https://github.com/JuliaLang/IJulia.jl/issues/18
Any volunteers?
Is there support in ipynb for hooking into the profiler?
-viral
Is there support in ipynb for hooking into the profiler?
What I meant to ask is whether ipynb understands how to format a backtrace, output of the performance profiler, or a debugger when we have one.
Currently these can all be strings, but the output could be prettier.
-viral
Yes, it is a big advantage to be doing this in the early stages of Julia, so that if the language or standard library has a problem we can just change it.I guess this include sending tracebacks as tokens instead of stings and some other stuff likethat where in IPython those are string with escape sequences we need to tokenize afterward...
What I meant to ask is whether ipynb understands how to format a backtrace, output of the performance profiler, or a debugger when we have one.
Currently these can all be strings, but the output could be prettier.
I'll take a look at the syntax highlighting. I rewrote the textmate syntax highlighting as one of the my first ever contributions. It'll be nice to come full circle. ;)
Warning: installing IJulia right now (https://github.com/JuliaLang/IJulia.jl) is not easy for casual users. You need bleeding-edge (git master) versions of a whole bunch of packages in addition to git master of Julia and IPython. However, I expect this to get easier shortly, once the following are addressed:
- Ubuntu system repositories install zmq version 2.x. Had to manually install zeromq version 3.2.3- Ubuntu system only had libgnutls26 installed. Also installed libgnutls28.
I have followed these simple instructions and installation works just fine. However, if I run "ipython console --profile=julia" it apparently launches a kernel but I can't communicate with it. Do you know what can be wrong, or how can I investigate the problem ? I don't even know on wich side (julia, ipython) the problem occurs.