generally---in recent
> julia-0.5
> builds, I have yet to notice an incorrect line number anywhere. One could
> construct examples where code is built up by expressions that
> (deliberately or
> not) get this wrong, but for any "typical" usage this appears to be fixed
Let me say again I love the language. However the error reporting is a
source of extreme frustration to me.
A key pathway to getting Julia more widely adopted would be for it to be
used for teaching purposes. However, at the moment I fear that any attempt
to do so would surely end in tears.
Pe
I have recently added a package for generating a variety of perceptually
uniform colour maps which may be of interest to you
https://github.com/peterkovesi/PerceptualColourMaps.jl
However I do not consider transparency
Cheers
Peter
On Friday, February 12, 2016 at 5:48:06 PM UTC+8, Patrick Kofod
I am encountering a problem whereby it seems that if Winston is imported
any subsequent calls to PyPlot produce a fatal Python error and the REPL
crashes
> using PyPlot
> plot(rand(20)) # All is OK
> import Winston # lots of deprecation messages
> plot(rand(20)) # crash
Fatal Python
Thanks Tom, yes it looks like a Tk problem
My matplotlib uses macosx as the backend. Winston uses the Tk package.
Importing Tk will result in subsequent calls to PyPlot crashing everything.
I was trying to use ImageView and PyPlot but ImageView uses Tk. I guess I
will have to unpackage the
Thanks Eric. Yes I appreciate that the language is highly flexible and one
can do lots of things. I don't want to get hung up on using indexing with
integer valued floats in particular, my concern is more philosophical
For much of what I do I am wanting to solve some technical problem within
Can I add a plea for allowing indexing with integers that are represented
by a floating point type
Following the principle of 'minimum surprise': If I have an integer just
that happens to be represented via a floating point type I would still like
to be able to use it as an integer.
After
