Hi all,
Since *yesterday* I have some trouble with pylab.
Some program hang. I cannot use Ctrl C to kill them.
Ctrl Z works. If I use ps I get
1091 pts/5 00:00:02 python
1119 pts/5 00:00:00 gs <defunct>
gs is somehow connected to my problem.
I can kill the job by kill -9 1091. Then the gs process (1119) also vanishes.
Any pointer ?
I am using svn from trunk.
Nils
Help us help you. Give us something to go on.
On Tuesday 24 June 2008 09:22:34 am Nils Wagner wrote:
Hi all,
Since *yesterday* I have some trouble with pylab.
Some program hang. I cannot use Ctrl C to kill them.
Ctrl Z works. If I use ps I get1091 pts/5 00:00:02 python
1119 pts/5 00:00:00 gs <defunct>gs is somehow connected to my problem.
I can kill the job by kill -9 1091. Then the gs process
(1119) also vanishes.Any pointer ?
I am using svn from trunk.
My fault -- I was working on adding an idle event handler across
backends and implemented something using threads for tkagg and haven't
solved the problem of cross thread signal handling. I've commented
out the functionality for now until I get it fixed (svn r5655). But
yes, Nils, at a minimum, the OS, backend, and svn revision number need
to be included in bug reports.
Thanks for the report,
JDH
On Tue, Jun 24, 2008 at 8:35 AM, Darren Dale <dsdale24@...149...> wrote:
On Tuesday 24 June 2008 09:22:34 am Nils Wagner wrote:
Hi all,
Since *yesterday* I have some trouble with pylab.
Some program hang. I cannot use Ctrl C to kill them.
Ctrl Z works. If I use ps I get1091 pts/5 00:00:02 python
1119 pts/5 00:00:00 gs <defunct>gs is somehow connected to my problem.
I can kill the job by kill -9 1091. Then the gs process
(1119) also vanishes.Any pointer ?
I am using svn from trunk.Help us help you. Give us something to go on.
Hi John, hi Daren,
Thank you for your prompt reply and sorry for my rudimental bug report.
BTW, is the transparency option for png files in progress ?
Cheers,
Nils
On Tue, 24 Jun 2008 08:59:30 -0500 "John Hunter" <jdh2358@...149...> wrote:
On Tue, Jun 24, 2008 at 8:35 AM, Darren Dale ><dsdale24@...149...> wrote:
On Tuesday 24 June 2008 09:22:34 am Nils Wagner wrote:
Hi all,
Since *yesterday* I have some trouble with pylab.
Some program hang. I cannot use Ctrl C to kill them.
Ctrl Z works. If I use ps I get1091 pts/5 00:00:02 python
1119 pts/5 00:00:00 gs <defunct>gs is somehow connected to my problem.
I can kill the job by kill -9 1091. Then the gs process
(1119) also vanishes.Any pointer ?
I am using svn from trunk.Help us help you. Give us something to go on.
My fault -- I was working on adding an idle event handler across
backends and implemented something using threads for tkagg and haven't
solved the problem of cross thread signal handling. I've commented
out the functionality for now until I get it fixed (svn r5655). But
yes, Nils, at a minimum, the OS, backend, and svn revision number need
to be included in bug reports.Thanks for the report,
JDH-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
matplotlib-devel List Signup and Options
I believe the unspoken consensus was it is easy to set the alpha on
the figurePatch and axesPatch so a global alpha was unneccessary.
Typically one wants the background to be translucent, but not every
figure element. If there is a use case where one wants *every*
figure element to be translucent with the same alpha, we can
reconsider. For PNGs however, postprocessing the alpha is easy, and
one can do this in mpl.
JDH
On Tue, Jun 24, 2008 at 9:17 AM, Nils Wagner <nwagner@...425...> wrote:
Thank you for your prompt reply and sorry for my rudimental bug report.
BTW, is the transparency option for png files in progress ?
That's a nasty problem. See
http://sebulba.wikispaces.com/recipe+thread2 for info, and IPython
implements that trick in Shell.py, look for HAS_CTYPES in there and
see the signal handlers that are in that section.
It's never 100% reliable, but the addition of this trick did help a
lot for -pylab. I don't know if it will do the trick for you.
Cheers,
f
On Tue, Jun 24, 2008 at 6:59 AM, John Hunter <jdh2358@...149...> wrote:
My fault -- I was working on adding an idle event handler across
backends and implemented something using threads for tkagg and haven't
solved the problem of cross thread signal handling.