I think using the profiler is the best bet here. We've used that in the
past to track down things that take a long time to import quite
successfully. I'm not seeing any slowness here, so that is likely do to
an environmental difference on your machine, implying you'll really need
to run the p
Resurrecting an old thread here
On Tue, Mar 29, 2011 at 3:23 PM, David Kremer wrote:
> > I would recommend running the import in the Python profiler to determine
> > where most of the time is going. When I investigated this a few years
> > back, it was mainly due to loading the GUI toolkits
I would recommend running the import in the Python profiler to determine
where most of the time is going. When I investigated this a few years
back, it was mainly due to loading the GUI toolkits, which are
understandably quite large. You can avoid most of that by using the Agg
backend. If you're
