With regards to defaults for 2.0, I am actually all for breaking them for
the better. What I find important is giving users an easy mechanism to use
an older style, if it is important to them. The current behavior isn't
"buggy" (for the most part) and failing to give users a way to get behavior
tha
I like the idea of aligning a set of changes for 2.0 even if still far
away.
Regarding to backwards compatibility I think that indeed it is important
but when changing mayor version (1.x to 2.0) becomes less important and we
must take care of prioritizing evolution.
Take for example the OO interf
Some of your wishes are in progress already:
https://github.com/matplotlib/matplotlib/pull/3818
There is also an issue open about scaling the dashes with the line width,
and you are right, the spacing for the dashes are terrible.
I can definitely see the argument to making a bunch of these visual
Hi all,
Since we're considering the possibility of making a matplotlib 2.0
release with a better default colormap, it occurred to me that it
might make sense to take this opportunity to improve other visual
defaults.
Defaults are important. Obviously for publication graphs you'll want
to end up t
On 2014/11/21, 4:42 PM, Nathaniel Smith wrote:
> On Fri, Nov 21, 2014 at 5:46 PM, Darren Dale wrote:
>> On Fri, Nov 21, 2014 at 12:32 PM, Phil Elson wrote:
>>>
>>> Please use this thread to discuss the best choice for a new default
>>> matplotlib colormap.
>>>
>>> This follows on from a discussio
On Fri, Nov 21, 2014 at 5:46 PM, Darren Dale wrote:
> On Fri, Nov 21, 2014 at 12:32 PM, Phil Elson wrote:
>>
>> Please use this thread to discuss the best choice for a new default
>> matplotlib colormap.
>>
>> This follows on from a discussion on the matplotlib-devel mailing list
>> entitled "How
I am a bit wary of doing a 2.0 _just_ to change the color map, but when
every I try to write out why, they don't sound convincing. We may end up
with a 3.0 within a year or so due to the possible plotting API/pyplot work
that is (hopefully) coming.
If we are going to do this, I think we should do
As a point of clarification, is this proposed 2.0 release different from
the 1.5 release?
On Fri, Nov 21, 2014 at 12:32 PM, Phil Elson wrote:
> Many of you will be aware of there has been an ongoing issue (#875,
> http://goo.gl/xLZvuL) which recommends the removal of Jet as the default
> colorma
On Fri, Nov 21, 2014 at 12:32 PM, Phil Elson wrote:
> Please use this thread to discuss the best choice for a new *default*
> matplotlib colormap.
>
> This follows on from a discussion on the matplotlib-devel mailing list
> entitled "How to move beyond JET as the default matplotlib colormap".
>
Many of you will be aware of there has been an ongoing issue (#875,
http://goo.gl/xLZvuL) which recommends the removal of Jet as the default
colormap in matplotlib.
The argument against Jet is compelling and I think that as a group who care
about high quality visualisation we should be seriously d
Please use this thread to discuss the best choice for a new *default*
matplotlib colormap.
This follows on from a discussion on the matplotlib-devel mailing list
entitled "How to move beyond JET as the default matplotlib colormap".
It is accepted that there can never be a *best* colormap for *all
11 matches
Mail list logo
