Eric Firing wrote:
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,
John Hunter wrote:
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
Norbert,
Either I am not understanding you correctly, or we have fundamentally
different views of the role of matplotlibrc values. The way I see it,
function args and kwargs *always* override matplotlibrc values, which in
turn *always* override built-in defaults. So in the example above, if
John Hunter wrote:
Eric == Eric Firing [EMAIL PROTECTED] writes:
This is, what is wanted in 99% of the cases and for every other
case, a rcfile-option will not help anyway.
Eric This sounds ideal to me--it makes everything simpler, both
Eric in the code and
John Hunter wrote:
Norbert == Norbert Nemec [EMAIL PROTECTED] writes:
Norbert This functionality was never there, so nobody can miss
Norbert it. Before my changes, the options in matplotlibrc only
Norbert allowed to specify fixed colors for mfc and mec. This is
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
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')
would set
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 any such
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 overridden
by
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
-
Take Surveys.
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 possible
to
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 '-' mean a solid
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) eliminate
Norbert,
Your 2790 patch seems to have completely wiped out the handling of
marker colors in the simple case N.plot(N.random.random(1000),'r.'),
as noted by Stefan Van der Walt in a message yesterday to the matplotlib
users list. I presume you are monitoring that list, and saw his message
Eric == Eric Firing [EMAIL PROTECTED] writes:
Eric So: please either restore your patch with additional changes
Eric to fix the problem Stefan found, or revert all of it cleanly
Eric until this can be sorted out.
Norbert -- can you describe briefly the inconsistencies in the format
OK, I understand. I will try sort out the problem today or otherwise
take back the whole patch.
I had not seen the message in matplotlib-users because of the backlog of
400 messages that have kept piling up...
Don't worry about additional confusion. Quickly reverting the patch was
the best thing
16 matches
Mail list logo
