On 7/24/07, Darren Dale <[EMAIL PROTECTED]> wrote: > On Tuesday 24 July 2007 11:29:22 am Fernando Perez wrote:
> > Bummer. It's nice to see that GUI for the whole of MPL running ;) > > I know, I really wanted to see this. Are you using traits from > http://code.enthought.com/enstaller/eggs/source/unstable? I think it has > something to do with my wx, maybe I am out of date, using wx-2.6.3.3: Mmh, dunno what the problem may be. I think I'm using a fairly old source install (of enthought), before eggs. All my machines are running Feisty. > > > > You can then save changes via > > > > > > > > mplconf2.write() > > > > > > The mpltest.py script expects there to be an mplrc2.conf file, but it > > > isnt in svn. So the script creates an empty mplrc2_copy.conf file, linked > > > with a default MPLConfig, but if I change some properties of > > > mplconf2.tconf, and then do mplconf2.write(), the mplrc2_copy.conf file > > > remains blank. > > > > Are you sure? I just ran the test removing the mplrc.conf file from > > my disk, and the mpnlrc2_copy.conf file is indeed created blank, but > > after editing the tconf object and calling write(), I *do* get the > > changes I make written to it. I can't reproduce your problem... > > I updated from svn. If mplrc.conf and mplrc2.conf are both present, I can run > mpltest.py, change mplconf2.tconf.backend.use, call mplconf2.write(), and get > a mplrc2_copy.conf that contains: > > # A hierarchical configuration > include = 'mplrc.conf' > [backend] > use = 'WxAgg' > > if I delete mplrc.conf, and repeat the exercise, I get a blank mplrc.conf, and > an mplrc2_copy.conf that contains: > > # A hierarchical configuration > include = 'mplrc.conf' > > If I delete mplrc2.conf, and I make sure that mplrc2_copy.conf has also been > deleted, the exercise yields a blank mplrc2_copy.conf. Just so we save time, would you mind just coding up the failure as a test? Something like (assuming it's inside mpltest.py, so the imports are done): def test(): ### if blah: raise Error('this is what I don't want') test() That way we know *exactly* what each other is trying to say. Maybe I'm just tired (I am), but I'm not quite understanding the problem you're seeing or the behavior you'd like/expect. > tconf2File works nicely. One comment, it is not indented like the files that > are created by tconf.write(), where sections are indented and subsections are > double-indented. Fixed to match the behavior of ConfigObj.write(), please update SVN. Cheers, f ------------------------------------------------------------------------- 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-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
