On Thursday 26 July 2007 11:40:23 am Fernando Perez wrote:
> On 7/26/07, Darren Dale <[EMAIL PROTECTED]> wrote:
> > On Thursday 26 July 2007 10:30:34 am Ted Drain wrote:
> > > Why do you need an api file at all? Why not have config be a python
> > > package and let config/__init__.py take care of
Darren Dale wrote:
> I am working on reorganizing our config system to work with Fernando's
> tconfig, and I could use some advice. Currently, a lot of the configuration
> code lives in __init__.py and rcsetup.py. I am thinking of a layout like
> this:
>
> matplotlib/lib/matplotlib/
> __ini
On Thursday 26 July 2007 02:29:26 pm Eric Firing wrote:
> Darren Dale wrote:
> > On Thursday 26 July 2007 10:39:22 am Tom Holroyd (NIH/NIMH) [E] wrote:
> >> Are traits going to be a dependency that I have to download and install,
> >> or will all the traits stuff be bundled with mpl?
> >
> > That h
Darren Dale wrote:
> On Thursday 26 July 2007 10:39:22 am Tom Holroyd (NIH/NIMH) [E] wrote:
>> Are traits going to be a dependency that I have to download and install, or
>> will all the traits stuff be bundled with mpl?
>
> That hasn't been determined yet.
Does your config system run with the ol
On 7/26/07, Darren Dale <[EMAIL PROTECTED]> wrote:
> On Thursday 26 July 2007 10:39:22 am Tom Holroyd (NIH/NIMH) [E] wrote:
> > Are traits going to be a dependency that I have to download and install, or
> > will all the traits stuff be bundled with mpl?
>
> That hasn't been determined yet.
Just a
On 7/26/07, Darren Dale <[EMAIL PROTECTED]> wrote:
> On Thursday 26 July 2007 10:30:34 am Ted Drain wrote:
> > Darren,
> > Well it wasn't one of your questions but...
> >
> > Why do you need an api file at all? Why not have config be a python
> > package and let config/__init__.py take care of imp
On Thursday 26 July 2007 10:39:22 am Tom Holroyd (NIH/NIMH) [E] wrote:
> Are traits going to be a dependency that I have to download and install, or
> will all the traits stuff be bundled with mpl?
I should also have mentioned, for those of you not following the older thread:
the new system is so
On Thursday 26 July 2007 10:39:22 am Tom Holroyd (NIH/NIMH) [E] wrote:
> Are traits going to be a dependency that I have to download and install, or
> will all the traits stuff be bundled with mpl?
That hasn't been determined yet.
--
Are traits going to be a dependency that I have to download and install, or
will all the traits stuff be bundled with mpl?
--
Tom Holroyd, Ph.D.
"The fundamentally misconceived nature versus nurture debate should be
abandoned: child development is inextricably both." -- Louann Brizendine
--
On Thursday 26 July 2007 10:30:34 am Ted Drain wrote:
> Darren,
> Well it wasn't one of your questions but...
>
> Why do you need an api file at all? Why not have config be a python
> package and let config/__init__.py take care of importing
> everything? The __init__ file of a package is respons
Darren,
Well it wasn't one of your questions but...
Why do you need an api file at all? Why not have config be a python
package and let config/__init__.py take care of importing
everything? The __init__ file of a package is responsible for
configuring the api of a package so it seems redunden
I am working on reorganizing our config system to work with Fernando's
tconfig, and I could use some advice. Currently, a lot of the configuration
code lives in __init__.py and rcsetup.py. I am thinking of a layout like
this:
matplotlib/lib/matplotlib/
__init__
...
config/
12 matches
Mail list logo
