> "Eric" == Eric Firing <[EMAIL PROTECTED]> writes:
Eric> 1) generate matplotlibrc with almost everything commented
Eric> out by default
+2
Hopefully, this will address the problem of all the deprecated rc
warnings people are getting, which is confusing to new users.
Eric> 2) el
> "Eric" == Eric Firing <[EMAIL PROTECTED]> writes:
Eric> It raises larger API questions. From the standpoint of
Eric> user-level code readability, the present array of marker and
Eric> line identifiers (inherited from Matlab) is not good. For
Eric> example, why should '-' me
Norbert,
>>> The core problem: The matplotlibrc file distributed with matplotlib
>>> contains all the default values in non-commented lines. This file is
>>> usually copied to the home-directory of any user, making it impossible
>>> to simply change any default value in later versions. It is not po
> "Eric" == Eric Firing <[EMAIL PROTECTED]> writes:
Eric> marker='tri_up')"? (I still don't know what is the
Eric> difference between "tri_up" and "triangle_up".)
tri_up is a tripod up, vs a triangle up.
JDH
-
Norbert,
>>
>>> The problem in r2790: I changed the default value in matplotlibrc to
>>> 'auto' and everything worked fine for me. I forgot that, of course,
>>> anybody updating from an older version, would still have the values
>>> 'blue' and 'black' in their matplotlibrc, which would not be ov
Norbert,
I am splitting this thread because I think different issues are involved
in different parts.
>
>> In looking at your original patch, I also wondered what is the reason
>> for supporting 3 different ways of specifying "_draw_nothing"? (I had
>> not previously noticed that there was a
> "Manuel" == Manuel Metz <[EMAIL PROTECTED]> writes:
Manuel> Hi, I just submitted a patch to sourceforge and also
Manuel> attached it to this email:
Manuel> The applied patch modifies the files axes.py and
Manuel> collections.py.
Manuel> I added a class StaredRegularPoly
Eric Firing wrote:
> Norbert Nemec wrote:
>
>> OK, I found the problem and committed a temporary fix. The real problem,
>> however is rooted a bit deeper.
>>
>> First an explanation of the intended change:
>>
>> It used to be that marker colors were partly automatic, but not
>> completely. I.e.
Norbert Nemec wrote:
> OK, I found the problem and committed a temporary fix. The real problem,
> however is rooted a bit deeper.
>
> First an explanation of the intended change:
>
> It used to be that marker colors were partly automatic, but not
> completely. I.e.
>
> plot(x,y,'-or')
>
> w
OK, I found the problem and committed a temporary fix. The real problem,
however is rooted a bit deeper.
First an explanation of the intended change:
It used to be that marker colors were partly automatic, but not
completely. I.e.
plot(x,y,'-or')
would set both, line color and marker color
10 matches
Mail list logo
