[IPython-dev] Small config puzzle
Sun Jun 3 18:35:28 CDT 2012
Doing so will add 1) docuemenation and 2) typing. Putting things into
dicts removes many of the benefits of our config system.
On Sun, Jun 3, 2012 at 4:34 PM, Brian Granger <email@example.com> wrote:
> I think that given our config system, the right solution is to move
> the keys of rc to be top-level config attributes.
> On Sun, Jun 3, 2012 at 4:26 PM, Fernando Perez <firstname.lastname@example.org> wrote:
>> On Sun, Jun 3, 2012 at 1:37 PM, Min RK <email@example.com> wrote:
>>> Overridden. The only thing you can do in config is simple attribute assignment. It doesn't do anything fancy, so c.InlineBackend.rc = foo is the same as doing the actual assignment to the real object.
>>> I don't know if you recall, but we discussed an API in your office to address this sort of thing for container traits, where we had an idea like:
>>> c.InlineBackend._rc_update = dict(foo=bar)
>>> for dicts or
>>> c.Foo._bar_extend = [more, entries]
>>> for lists.
>> Yup, now I remember, and it might have been triggered by me trying to
>> mess around with this same guy. Though I still worry that it may be a
>> lot of special-case knowledge to expect users to remember... I feel
>> like we haven't quite hit completely the sweet spot with the api for
>> this part (though by and large it works very well, given how complex
>> the problem it's faced with is).
>> IPython-dev mailing list
> Brian E. Granger
> Cal Poly State University, San Luis Obispo
> firstname.lastname@example.org and email@example.com
Brian E. Granger
Cal Poly State University, San Luis Obispo
firstname.lastname@example.org and email@example.com
More information about the IPython-dev