Dear Matplotlib Folks,
When I run pylab.plot, I get a weird warning:
** (python:20754): WARNING **: Couldn't connect to system bus
** (python:20754): WARNING **: Couldn't connect to system bus
<matplotlib.lines.Line2D object at 0x1225850>
(Note that this was copied by hand because the system on which I run
Matplotlib is currently unable to connect to the global internet.)
The first line really is repeated.
The number after "python:" changes from one instance of the warning to
another.
I am running:
Red Hat Enterprise Linux ES release 4 (Nahant Update 3)
At least, that is what is in /etc/redhat-release.
The warning is not fatal and I can display what I attempted to plot with
pylab.show. However, the warning has a significant impact on the
interactive usability of Python and matplotlib as a replacement for Matlab.
Anyone have any suggestions or observations?
Yours,
David Sigeti
···
--
View this message in context: http://www.nabble.com/Warning-from-pylab.plot-on-Linux-tp22793709p22793709.html
Sent from the matplotlib - users mailing list archive at Nabble.com.
Which backend are you using? I suspect this is actually a bug in the GUI framework being used, which we could rule out by running a simple script to do something basic (like show a window) and see if we get the same warning.
Mike
sigeti wrote:
···
Dear Matplotlib Folks,
When I run pylab.plot, I get a weird warning:
** (python:20754): WARNING **: Couldn't connect to system bus
** (python:20754): WARNING **: Couldn't connect to system bus
<matplotlib.lines.Line2D object at 0x1225850>
(Note that this was copied by hand because the system on which I run
Matplotlib is currently unable to connect to the global internet.)
The first line really is repeated.
The number after "python:" changes from one instance of the warning to
another.
I am running:
Red Hat Enterprise Linux ES release 4 (Nahant Update 3)
At least, that is what is in /etc/redhat-release.
The warning is not fatal and I can display what I attempted to plot with
pylab.show. However, the warning has a significant impact on the
interactive usability of Python and matplotlib as a replacement for Matlab.
Anyone have any suggestions or observations?
Yours,
David Sigeti
--
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA
Dear Mike and Jouni,
Since my post from yesterday, I have discovered that I was using the
WXApp backend and that using the TkApp backend fixed the problem.
Thanks for the help and sorry about the naive question. I am almost
completely new to Matplotlib and am only now getting my
bearings.
That said, I have another question: Are there any important implications
to the spurious warnings coming from WXApp? I don’t know how
functional WXApp is expected to be at this point nor even if this problem
really precludes using it. For all I know there might be a simple
work-around or there might really be no reason at all to use WXApp rather
than TkApp. Any light that you can shed here would be much
appreciated.
A couple of further observations:
- As I pointed out, pyplot.show appears to work fine in spite of the
warning message. The resulting plot window, however, shows a number
of peculiarities in behavior and seems to be missing functionality that
the corresponding TkApp window has. All this suggests to me that
the WXApp backend may not really be fully functional yet. Any
observations or comments?
- wxPython itself seems to work fine. At least, that is what I
see from running the demos.
Again, thanks for the help and any further comments, observations,
advice will be much appreciated.
Yours,
David
···
At 08:41 AM 3/31/2009, Michael Droettboom wrote:
Which backend are you using? I
suspect this is actually a bug in the GUI framework being used, which we
could rule out by running a simple script to do something basic (like
show a window) and see if we get the same warning.
Mike
sigeti wrote:
Dear Matplotlib Folks,
When I run pylab.plot, I get a weird warning:
** (python:20754): WARNING **: Couldn’t connect to system bus
** (python:20754): WARNING **: Couldn’t connect to system bus
<matplotlib.lines.Line2D object at 0x1225850>
(Note that this was copied by hand because the system on which I run
Matplotlib is currently unable to connect to the global
internet.)
The first line really is repeated.
The number after “python:” changes from one instance of the
warning to
another.
I am running:
Red Hat Enterprise Linux ES release 4 (Nahant Update 3)
At least, that is what is in /etc/redhat-release.
The warning is not fatal and I can display what I attempted to plot
with
pylab.show. However, the warning has a significant impact on
the
interactive usability of Python and matplotlib as a replacement for
Matlab.
Anyone have any suggestions or observations?
Yours,
David Sigeti
–
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA
Dr. David E. Sigeti
Phone: 505-667-9239
E-mail: sigeti@…652…
Surface mail: MS-F644, Los Alamos National Laboratory,
Los Alamos, NM 87545 USA
Friends,
Oops! “WXAgg” and “TkAgg” rather than
“WXApp” and “TkApp”, of course. I did say that
I was just getting my bearings.
Yours,
David
···
At 12:13 PM 3/31/2009, David E. Sigeti wrote:
Dear Mike and Jouni,
Since my post from yesterday, I have discovered that I was using the
WXApp backend and that using the TkApp backend fixed the problem.
Thanks for the help and sorry about the naive question. I am almost
completely new to Matplotlib and am only now getting my
bearings.
That said, I have another question: Are there any important implications
to the spurious warnings coming from WXApp? I don’t know how
functional WXApp is expected to be at this point nor even if this problem
really precludes using it. For all I know there might be a simple
work-around or there might really be no reason at all to use WXApp rather
than TkApp. Any light that you can shed here would be much
appreciated.
A couple of further observations:
- As I pointed out, pyplot.show appears to work fine in spite of the
warning message. The resulting plot window, however, shows a number
of peculiarities in behavior and seems to be missing functionality that
the corresponding TkApp window has. All this suggests to me that
the WXApp backend may not really be fully functional yet. Any
observations or comments?
- wxPython itself seems to work fine. At least, that is what I
see from running the demos.
Again, thanks for the help and any further comments, observations,
advice will be much appreciated.
Yours,
David
At 08:41 AM 3/31/2009, Michael Droettboom wrote:
Which backend are you using? I
suspect this is actually a bug in the GUI framework being used, which we
could rule out by running a simple script to do something basic (like
show a window) and see if we get the same warning.
Mike
sigeti wrote:
Dear Matplotlib Folks,
When I run pylab.plot, I get a weird warning:
** (python:20754): WARNING **: Couldn’t connect to system bus
** (python:20754): WARNING **: Couldn’t connect to system bus
<matplotlib.lines.Line2D object at 0x1225850>
(Note that this was copied by hand because the system on which I run
Matplotlib is currently unable to connect to the global
internet.)
The first line really is repeated.
The number after “python:” changes from one instance of the
warning to
another.
I am running:
Red Hat Enterprise Linux ES release 4 (Nahant Update 3)
At least, that is what is in /etc/redhat-release.
The warning is not fatal and I can display what I attempted to plot
with
pylab.show. However, the warning has a significant impact on
the
interactive usability of Python and matplotlib as a replacement for
Matlab.
Anyone have any suggestions or observations?
Yours,
David Sigeti
–
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA
Dr. David E. Sigeti
Phone: 505-667-9239
E-mail: sigeti@…652…
Surface mail: MS-F644, Los Alamos National Laboratory,
Los Alamos, NM 87545 USA
Dr. David E. Sigeti
Phone: 505-667-9239
E-mail: sigeti@…652…
Surface mail: MS-F644, Los Alamos National Laboratory,
Los Alamos, NM 87545 USA