Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

master breaks PyPlot #176

Closed
yuyichao opened this issue Jul 29, 2015 · 9 comments
Closed

master breaks PyPlot #176

yuyichao opened this issue Jul 29, 2015 · 9 comments

Comments

@yuyichao
Copy link
Collaborator

I checked out the PyCall master today and got the following error when importing PyPlot

julia> using PyPlot
/usr/lib/python3.4/site-packages/matplotlib/__init__.py:1318: UserWarning:  This call to matplotlib.use() has no effect
because the backend has already been chosen;
matplotlib.use() must be called *before* pylab, matplotlib.pyplot,
or matplotlib.backends is imported for the first time.

  warnings.warn(_use_error_msg)
WARNING: error initializing module PyPlot:
PyCall.PyError(msg=":PyImport_ImportModule", T=PyCall.PyObject(o=0x00007ffdda4be380), val=PyCall.PyObject(o=0x00007ffdcc2c6c18), traceback=PyCall.PyObject(o=0x00007ffdcc043448))

Haven't investigate further but downgrading to 0.8.2 release fixes the issue.

@stevengj
Copy link
Member

Works for me using the master of PyCall and PyPlot.

@yuyichao
Copy link
Collaborator Author

Maybe python2 vs python3?

@stevengj
Copy link
Member

I'm using Python 2. What system are you on, and what backend is matplotlib using?

@yuyichao
Copy link
Collaborator Author

ArchLinux x64. Python 3.4.3. Matplotlib 1.4.3,

% cat ~/.config/matplotlib/matplotlibrc
backend: Qt4Agg

@yuyichao
Copy link
Collaborator Author

And julia master

julia> versioninfo()
Julia Version 0.4.0-dev+6350
Commit 9b14a7c* (2015-07-29 10:26 UTC)
Platform Info:
  System: Linux (x86_64-unknown-linux-gnu)
  CPU: Intel(R) Core(TM) i7-4702HQ CPU @ 2.20GHz
  WORD_SIZE: 64
  BLAS: libopenblas (DYNAMIC_ARCH NO_AFFINITY Haswell)
  LAPACK: libopenblas
  LIBM: libm
  LLVM: libLLVM-3.6.1

@stevengj
Copy link
Member

Could this be related to #177?

@yuyichao
Copy link
Collaborator Author

Not really the same (although could be related). #177 is happening on the released version while I only see this on master.

@stevengj
Copy link
Member

You might try a Pkg.update() again to see if has been fixed by the recent PyCall updates.

@yuyichao
Copy link
Collaborator Author

It was broken sometime last week but seems to be fine now. Anyway, the original issue has been solved a long time ago (since it was working for sometime last month...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants