2008/1/9, Darren Dale <[EMAIL PROTECTED]>: > > setup.py attempts to select the appropriate backend for you, based on what > backends were available at build time. That selection is written into the > default matplotlibrc file, which resides in > site-packages/matplotlib/mpl-data. If matplotlib finds another matplotlibrc > file (for example, in the current working directory, in $HOME/.matplotlib, > etc), then it will use those settings instead. I would guess that is the > source of the problem. >
No, the problem is the default installed matplotlibrc, that is not different from the one present in the source tree and has the default selection: backend : TkAgg Now, i don't know if the build script is trying to modify it according user selection or compile-time backend detection, but I'm wondering why the same problem wasn't happening on linux, where I tipically never install Tk runtime. However, for me the problem is solved, but if there's a matplotlib windows dev listening, here is my experience; first, i removed the already installed "lib/site-packages/matplotlib/mpl-data/matplotlibrc" . Afer, I went for clean compiling with a setup.cfg with these configurations: gtk = True gtkagg = False tkagg = False wxagg = False backend = GTK Eventually, "python setup.py install" write again a "site-packages/matplotlib/mpl-data/matplotlibrc" which still have: backend : TkAgg If this shouldn't happen, well, consider this a bug report :D Greetings, Francesco Pretto ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
