There seems to be some breakage right now in Anaconda from their switch
from Qt4 to Qt5. Updating to PyCall and PyPlot master, and forcing the
Qt4Agg backend (e.g. with ENV["MPLBACKEND"]="Qt4Agg") should work.
Dear all,
sorry for not replying before but I've been very busy lately... Still I
wanted to report back here. While I found some of teh previous solutions to
work, I finally found out there was a bad interaction between Anaconda's
Python and julia. SImply got rid of Anaconda and then
Hello colleague,
On Thursday, September 29, 2016 at 9:36:43 AM UTC+2, Ferran Mazzanti wrote:
>
> Nobody is using PyPlot under OSX, please?
>
your description of the error/failure is quite broad. Please file an issue
to the package and provide details.
I'm not a OSX user (and also not pyplot),
Have you tried the latest master?
Pkg.checkout("PyPlot", "master")
Otherwise revert to an older version and try that. I think from within
Julia you'd have to edit the REQUIRE file (or is there an easier way?).
Probably ~/.julia/v0.5/REQUIRE or ~/.julia/v0.4/REQUIRE, modify the line
with PyPlot.
Nobody is using PyPlot under OSX, please?
Best,
Ferran.
On Wednesday, September 28, 2016 at 10:35:58 AM UTC+2, Ferran Mazzanti
wrote:
>
> Hi,
>
> it seems that PyPlot is still broken in 0.5.0 and OSX, at least
> Mavericks... Anybody else has faced this problem? If yes, how can I solve
> it? If
Hi,
it seems that PyPlot is still broken in 0.5.0 and OSX, at least
Mavericks... Anybody else has faced this problem? If yes, how can I solve
it? If not, what versions of PyCall/PyPlot are you using? The ones I was
told to use here still work, but spit quite a lot of warnings etc... and it
is
At Github :)
https://github.com/stevengj/PyCall.jl/issues/new for PyCall
or
https://github.com/stevengj/PyPlot.jl/issues/new for PyPlot
On Thursday, August 18, 2016 at 9:42:49 PM UTC+2, Ferran Mazzanti wrote:
>
> Yes of course... how do I do that?
> Thanks,
> Ferran.
>
> On Thursday, August
Yes of course... how do I do that?
Thanks,
Ferran.
On Thursday, August 18, 2016 at 8:29:08 PM UTC+2, Steven G. Johnson wrote:
>
> Please file an issue if the latest version of PyCall (or PyPlot) is
> failing for you.
>
Please file an issue if the latest version of PyCall (or PyPlot) is failing
for you.
Hi again,
thanks all of you for the replies. And specially to Bart, who gave me the
precise information. I just did:
Pkg.pin("PyCall",v"1.4.0")
Pkg.pin("PyPlot",v"2.1.1")
Pkg.build("PyPlot")
and from there
using PyPlot
did the trick :)
Cheers,
Ferran.
Pkg.pin(packageName, version) should force a package at a particular
version. Unfortunately, depending on how package dependencies have been set
up, older versions of the package might still be happy to work with newer
versions of the dependencies, and that might trigger the bug you are
Hello colleague,
On Thursday, August 18, 2016 at 10:47:27 AM UTC+2, Ferran Mazzanti wrote:
>
> Dear all,
>
> looks like lots of messing around with versions had rendered PyPlot
> unusable in 0.4.6 under OSX (at least).
> Now I need to do some work that requires its use so I need to have it up
>
12 matches
Mail list logo
