There is a proof-of-concept implementation of this by Matthias
http://carreau.github.io/posts/09-Matplotlib-And-IPython-Config.html
Tom
On Fri, May 15, 2015 at 4:40 PM Brian Granger elliso...@gmail.com wrote:
OK i have the MEP for this on my todo list...
On Thu, May 14, 2015 at 5:47 AM,
OK i have the MEP for this on my todo list...
On Thu, May 14, 2015 at 5:47 AM, Benjamin Root ben.r...@ou.edu wrote:
You could start up a Pull Request describing a MEP that would outline how
traitlets would be used. The discussion can go on there to flesh out the
concepts and the guidance
You could start up a Pull Request describing a MEP that would outline how
traitlets would be used. The discussion can go on there to flesh out the
concepts and the guidance documentation. Once that is agreed upon, that PR
would get merged, and we can then start up a new PR actually implementing
I should note that *all* of ipython is based on traitlets, so by now it is
very stable, battle tested (also actively developed). For base layers like
this, I think that is important.
On Wed, May 13, 2015 at 11:27 PM, Neil Girdhar mistersh...@gmail.com
wrote:
This is very exciting! traitlets
This is very exciting! traitlets looks really nice. (Imho better than
params from my cursory look.)
On Thu, May 14, 2015 at 1:45 AM, Brian Granger elliso...@gmail.com wrote:
We (ipython/jupyter) have been talking some more about integrating
matplotlilb in deeper ways with the interactive
It is my understanding that most of this code pre-dates properties and
going through and updating all of the classes is a _huge_ amount of work.
It is more a matter of time than will.
There is also a slowly simmering discussion about implementing artists in a
managed property/attribute frame
Manpower, really. Also, there be dragons deep in that code (I'll leave it
as an exploration task for you to figure out how aliases are done).
There have been a few proposals, but they keep suffering from scope creep.
Take a look at the MEP page.
Keep in mind that reducing Lines of Code just for
You're right. My angle is I just want the setters and getters. Writing
set_ and get_ feels like the C++ prison I thought I had escaped :)
I'll keep an eye for the discussion on this topic since this is interesting
to me for other reasons as well. (I had to code something like params for
my own
We (ipython/jupyter) have been talking some more about integrating
matplotlilb in deeper ways with the interactive widgets framework. That
only thing that would be required to make this *trivial* is having a
traitlet's based API for matplotlib. I have even started to look at
wrapping the existing
On 2015/05/13 5:47 PM, Neil Girdhar wrote:
You're right. My angle is I just want the setters and getters. Writing
set_ and get_ feels like the C++ prison I thought I had escaped :)
John Hunter once commented that if he were doing it over again he would
not have put in all the set_ and get_;
10 matches
Mail list logo
