Re: [matplotlib-devel] rcparams/traits

2007-07-25 Thread Darren Dale
On Tuesday 24 July 2007 11:17:32 pm Fernando Perez wrote: On 7/24/07, Darren Dale [EMAIL PROTECTED] wrote: On Tuesday 24 July 2007 7:28:59 pm Fernando Perez wrote: :) That should be plenty of information. One comment: if you load : mplrc2.conf, which includes an mplrc.conf with a bogus

Re: [matplotlib-devel] rcparams/traits

2007-07-25 Thread Fernando Perez
On 7/25/07, Darren Dale [EMAIL PROTECTED] wrote: Not so much. I just wanted to give thorough feedback (No, I'm not *trying* to drive you crazy). Don't worry, the damage was done long ago :) More seriously, I do appreciate the feedback. It was very good to have someone at the other end

[matplotlib-devel] rcparams/traits

2007-07-24 Thread Fernando Perez
Hi all, if anyone is still following, please update the tconfig work. Run ipython -wthread %run mpltest.py mplconf2.tconf.edit_traits() Edit to your heart's content. You can then save changes via mplconf2.write() Cheers, f ps - the auto-generated file now has all class docstrings as

Re: [matplotlib-devel] rcparams/traits

2007-07-24 Thread John Hunter
On 7/24/07, Fernando Perez [EMAIL PROTECTED] wrote: Hi all, if anyone is still following, please update the tconfig work. Run ipython -wthread %run mpltest.py mplconf2.tconf.edit_traits() Edit to your heart's content. I am not running in wthred, but I think there may be an import

Re: [matplotlib-devel] rcparams/traits

2007-07-24 Thread Darren Dale
On Tuesday 24 July 2007 5:20:40 am Fernando Perez wrote: Hi all, if anyone is still following, please update the tconfig work. Run ipython -wthread %run mpltest.py mplconf2.tconf.edit_traits() Edit to your heart's content. I can't get edit_traits() working on my machine, but I can do it

Re: [matplotlib-devel] rcparams/traits

2007-07-24 Thread Fernando Perez
On 7/24/07, Darren Dale [EMAIL PROTECTED] wrote: On Tuesday 24 July 2007 5:20:40 am Fernando Perez wrote: Hi all, if anyone is still following, please update the tconfig work. Run ipython -wthread %run mpltest.py mplconf2.tconf.edit_traits() Edit to your heart's content. I

Re: [matplotlib-devel] rcparams/traits

2007-07-24 Thread Fernando Perez
On 7/24/07, Darren Dale [EMAIL PROTECTED] wrote: On Tuesday 24 July 2007 7:57:37 am John Hunter wrote: On 7/24/07, Fernando Perez [EMAIL PROTECTED] wrote: Hi all, if anyone is still following, please update the tconfig work. Run ipython -wthread %run mpltest.py

Re: [matplotlib-devel] rcparams/traits

2007-07-24 Thread Darren Dale
On Tuesday 24 July 2007 11:29:22 am Fernando Perez wrote: On 7/24/07, Darren Dale [EMAIL PROTECTED] wrote: On Tuesday 24 July 2007 5:20:40 am Fernando Perez wrote: Hi all, if anyone is still following, please update the tconfig work. Run ipython -wthread %run mpltest.py

Re: [matplotlib-devel] rcparams/traits

2007-07-24 Thread Darren Dale
Hi Fernando, On Tuesday 24 July 2007 1:34:47 pm Fernando Perez wrote: Just so we save time, would you mind just coding up the failure as a test? It is attached. Here is the output on my machine: copying mplrc.conf to mplrc_copy.conf loading from mplrc_copy.conf Backend loaded from file:

Re: [matplotlib-devel] rcparams/traits

2007-07-24 Thread Fernando Perez
On 7/24/07, Darren Dale [EMAIL PROTECTED] wrote: Hi Fernando, On Tuesday 24 July 2007 1:34:47 pm Fernando Perez wrote: Just so we save time, would you mind just coding up the failure as a test? It is attached. Here is the output on my machine: Great, thanks. Please update. My comments

Re: [matplotlib-devel] rcparams/traits

2007-07-24 Thread Darren Dale
On Tuesday 24 July 2007 5:49:27 pm Fernando Perez wrote: On 7/24/07, Darren Dale [EMAIL PROTECTED] wrote: creating RecursiveConfManager with no_mplrc.conf, which does not exist calling RecursiveConfigManagers write() method Here are the contents of no_mplrc.conf: I might have expected

Re: [matplotlib-devel] rcparams/traits

2007-07-24 Thread Fernando Perez
On 7/24/07, Darren Dale [EMAIL PROTECTED] wrote: Thank you for all you have already done, Fernando. My pleasure. I hope this will be useful for all of us, and that we can offer to users unified mechanisms for dealing with the various pieces of the 'scientific python toolkit' puzzle. I tried