On Dec 5, 2007 8:58 AM, José Gómez-Dans <[EMAIL PROTECTED]> wrote:
> Mmmm... I was just wondering whether compiling the new 0.91.1 version might
> make the problem go away? I am currently running 0.90.1.
Unlikely, we haven't changed anything in that code. One thing you can
do, it is fairly labor
On Tuesday 04 December 2007 16:16:06 José Gómez-Dans wrote:
> On Tuesday 04 December 2007 16:05:33 John Hunter wrote:
> > On Dec 4, 2007 10:00 AM, José Gómez-Dans <[EMAIL PROTECTED]> wrote:
> > Hmm, the plot thickens. How about embedding_in_gtk2.py -- this add the
> > toolbar
>
> This does indeed
On Tuesday 04 December 2007 16:05:33 John Hunter wrote:
> On Dec 4, 2007 10:00 AM, José Gómez-Dans <[EMAIL PROTECTED]> wrote:
> > Interestingly enough, the embedding_in_gtk.py script works perfectly
> > (takes less than a second to run), so I am not able to reproduce the
> > slowness!
>
> Hmm, the
On Dec 4, 2007 10:00 AM, José Gómez-Dans <[EMAIL PROTECTED]> wrote:
> Interestingly enough, the embedding_in_gtk.py script works perfectly (takes
> less than a second to run), so I am not able to reproduce the slowness!
Hmm, the plot thickens. How about embedding_in_gtk2.py -- this add the toolb
On Tuesday 04 December 2007 15:54:17 you wrote:
> OK, it is in the gtk figure creation code. Get the matplotlib
> examples directory and try running examples/embedding_in_gtk.py which
> does not use pylab but instead does all the gtk stuff manually. See
> if you can reproduce the error. If so, s
On Dec 4, 2007 9:39 AM, José Gómez-Dans <[EMAIL PROTECTED]> wrote:
> On Tuesday 04 December 2007 15:31:04 John Hunter wrote:
> > What about these scripts
> >
> > # just make a figure
> > from pylab import *
> > figure()
>
> Takes a long time.
OK, it is in the gtk figure creation code. Get the mat
On Tuesday 04 December 2007 15:31:04 John Hunter wrote:
> What about these scripts
>
> # just make a figure
> from pylab import *
> figure()
Takes a long time.
> # just make a subplot
> from pylab import *
> subplot(111)
Takes a long time.
> I'm trying to narrow down where the problem is occurr
On Dec 4, 2007 9:19 AM, José Gómez-Dans <[EMAIL PROTECTED]> wrote:
> On Tuesday 04 December 2007 15:13:21 you wrote:
> > OK, the delay comes before draw which is an important piece of
> > information. What happens if you run these two scripts. Do you get
> > the delay?
> >
> > # script 1 (no plot
On Tuesday 04 December 2007 15:13:21 you wrote:
> OK, the delay comes before draw which is an important piece of
> information. What happens if you run these two scripts. Do you get
> the delay?
>
> # script 1 (no plot)
> from pylab import *
No delay. Debug output stops at line "backend GTKAgg
On Tuesday 04 December 2007 14:27:21 you wrote:
> On Dec 4, 2007 8:23 AM, José Gómez-Dans <[EMAIL PROTECTED]> wrote:
> > PS and Agg work fast enough, and produce meaningful PS and PNG output
> > files (as well as popping up a window with the plot)
>
> Wait a minute, if you are getting a plot window
On Dec 4, 2007 8:23 AM, José Gómez-Dans <[EMAIL PROTECTED]> wrote:
> PS and Agg work fast enough, and produce meaningful PS and PNG output files
> (as well as popping up a window with the plot)
Wait a minute, if you are getting a plot window when you pass -dPS or
-dAgg, something very odd is happ
On Dec 4, 2007 8:23 AM, José Gómez-Dans <[EMAIL PROTECTED]> wrote:
> PS and Agg work fast enough, and produce meaningful PS and PNG output files
> (as well as popping up a window with the plot)
Wait a minute, if you are getting a plot window when you pass -dPS or
-dAgg, something very odd is happ
John,
On Tuesday 04 December 2007 14:07:36 you wrote:
> Two more tests. WIll you set the debug level to
> --verbose-debug-annoying and add a savefig command to your script, eg
> savefig('myfig') with no extension (the backend will provide a default
> extension with the -d flags below). Try runni
On Dec 4, 2007 4:50 AM, José Gómez-Dans <[EMAIL PROTECTED]> wrote:
> Thanks for your reply. I think it might well be a fonts problem. Here's the
> test script, plus a comment where the big delay happens:
> % cat test.py
> from pylab import *
> plot([1,2,3])
> show()
Two more tests. WIll you set
John,
On Tuesday 04 December 2007 03:25:15 John Hunter wrote:
> On Dec 3, 2007 9:08 AM, José Gómez-Dans <[EMAIL PROTECTED]> wrote:
> > I have compiled v.0.90.1 on RHEL 5. By default, the GTKAgg backend is
> > being used (TkAgg cannot be set, as TkInter is not installed on the
> > system, I think.
On Dec 3, 2007 9:08 AM, José Gómez-Dans <[EMAIL PROTECTED]> wrote:
> Hi,
> I have compiled v.0.90.1 on RHEL 5. By default, the GTKAgg backend is being
> used (TkAgg cannot be set, as TkInter is not installed on the system, I
> think. It throws a "NO Module named Tkinter" error).
>
> At any rate, a
Hi,
I have compiled v.0.90.1 on RHEL 5. By default, the GTKAgg backend is being
used (TkAgg cannot be set, as TkInter is not installed on the system, I
think. It throws a "NO Module named Tkinter" error).
At any rate, a test session is as follows:
import pylab
pylab.plot ( [1,2,3],[1,2,3],'-or')
17 matches
Mail list logo
