>> somehow connected to the pylab mode of Ipython.
>> >
>> > Cheers,
>> > Derek
>> >
>> > --
>> > Anaconda Community Support Group Brought to you by Continuum Analytics
>> > ---
>> > You rec
Hi Derek,
> the framework. Though, if I understand correctly, Anaconda provides a
> framework version of the interpreter
> pythonw and a non-frameworked python?
This is right -- the GUI backends to matplotlib cause python to crash, but
not pythonw. This is annoying, since the two binaries
are e
allbacks.
>>
>> What I'd love to see is some enhancement of the backend framework where
>> there are some extra flags and information passed to the renderer: i.e. for
>> each draw command, we need to know whether the drawn object should be
>> linked to static figu
lf at http://plotornot.chrisbeaumont.org .
Plot or Not was mostly a tongue-in-cheek idea, but there is nonetheless
some interesting information about style preferences in these data. I'm
happy to share the raw vote data if anyone is interested in digging further.
Cheers,
Hi Damon,
Thanks for your thoughts on how this should fit in with MPLs API. My $0.02:
What would feel more natural is if I could do the following:
> f = Facet(...)
> ax.facet(f, 'scatter')
>
Three things about this style bother me:
1. It seems too verbose ("facet" gets typed a lot -- 4 times if
Pandas has some nice tools to make faceted plots -- small multiples of
plots where data is grouped by category (
http://pandas.pydata.org/pandas-docs/stable/rplot.html). However, I think
there would be value in having this functionality built into matplotlib.
Mainly:
1. Not every dataset lives in
I'd like to sit in on this if I'm available. Please keep me posted
Cheers,
Chris
--
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So wha
d diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> ___
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo
I had the same question about opt-out vs opt-in. Personally, I vote for
opt-out. I would like to see each release of MPL have an associated style
(which may be the same as the last release, but maybe not). With Tony's
style PR, users that need constant styles would either put
`style.use('1.3')` in
ppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _
arams.
Sorry for being long-winded -- I just want to make the case that this is an
important (and not *entirely* subjective) issue. If nothing else, it would
be great to see some clear statement about where the MPL devs stand on this
issue -- what criteria must be met to consider a change to the defaults
11 matches
Mail list logo
