Chris wrote: > Updating matplotlib with a new SVN build a couple days ago induced > the following error: > > RuntimeError: matplotlib.use() must be called *before* pylab > or matplotlib.backends is imported for the first time. > > This has not occurred before. Am I to understand that once pylab > is imported, you cannot change backends? That seems strange. Is > there a way of side-stepping this?
This has long been the case, but only recently was an error added. (It was confusing to many who *thought* they were changing the backend, when in fact they weren't.) I don't know of any way to side step this -- for various reasons, the backend must be known during pylab initialization. It might be possible with fairly significant refactoring... maybe someone has looked deeper into this than I have. Cheers, Mike -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
