I got some input
before continuing. I have now gotten far enough to know that the base code
should work without any more tweaking.
Best,
OceanWolf
--
View this message in context:
http://matplotlib.1069221.n5.nabble.com/MEP-27-Backend-Refactor-Gcf-tp45032.html
Sent from the matplotlib - devel m
(which of the
backends I have converted, seems the most obfuscated of them all) and
have just finished reading through, and marking up the code with TODOs
ready for refactor of that backend. I will also update the MEP page to
flesh out parts that I feel need more detail.
Best,
OceanWolf
Tom, ``When we drop numpy 1.5''? I thought we already had... I mean we
only test numpy 1.6 on Travis...
For the rebinning exercise, I don't have time to look, but I would
expect a similar trick to imshow, quiver, etcetera when I want to
compare to a baseline (e.g. for animation). Namely I cal
interface, but that's not what I think you're describing. A better
practice, IMO is to raise a DeprecationWarning when the
soon-to-be-removed code is executed. Then you can just grep for those
and get cracking.
-p
On Tue, Mar 10, 2015 at 8:51 AM OceanWolf
mailto:juichenieder-n...@y
Slightly off-topic, does github allow for one to tag lines/code-blocks
with notes to the future like ``numpy1.5 removal'', similar to tags for
issues and milestones? This would save us from trawling through the
code looking for comments. If github does not have this feature, do you
think gith
main branch merged we can then progress/finalise MEPs 22 and 23.
On 02/03/15 20:20, OceanWolf wrote:
> Hi everyone,
> Over the past week or so I have been working on what I now dub MEP27
> <https://github.com/matplotlib/matplotlib/wiki/MEP27> . I have already
> gotten quite far wi
on of that.
On 24/03/15 06:58, Achyut Rastogi wrote:
Changes made during refactors are always backwards compatible right? I
just wanted to know what you mean by "breaking the main PR"?
Thank you
On Mon, Mar 23, 2015 at 10:30 PM, OceanWolf
mailto:juichenieder-n...@yahoo.co.uk>>
wr
Okay, just about finished WebAgg, but it has raised an interesting
question about layout...
I started working to standardise using the way we do it on ``Gtk3``,
i.e. using a pure vertical layout, adding elements from either the top
or the bottom of the container and setting widgets (i.e. the can
llusion in the other or not.
Finally a bit confused as to what all the lines mean, any chance of some
annotation? Also I would find it helpful to see a version without the
big red line and what it looks like in practice (see the doc for the
test script).
Best,
OceanWolf
On 05/04/15 23:18, Olga
Not sure why my message didn't go through earlier, but yes, the issue
already exists in the system, see
https://github.com/matplotlib/matplotlib/issues/4092
On 07/04/15 19:07, Benjamin Root wrote:
Yes, this was discovered recently in connection to changes in how idle
events were handled. I don
Personally, just looking at the images I think B looks more
professional, the others look faded. With A and B I see more of
"contrast" in the core of the radial image (though that might arise from
a combination of my monitor/eyes, though I usually do quite well in
colour perception tests).
I
bugs, though I doubt we will have any O:)).
Best,
OceanWolf
--
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/list
on't break everything.
Meh, perhaps I just act too overcautious.
From: Thomas Caswell
To: OceanWolf ;
"matplotlib-devel@lists.sourceforge.net"
Sent: Wednesday, 17 June 2015, 6:04
Subject: Re: [matplotlib-devel] Release schedule
I am not sur
Ooh, I do like Eric's v2, I see much more of a fall off in the sample images,
so I would say v2 > D > ?
Any chance of the galaxy animation with v2?
Another question, why does a reason exist why the colour-maps start at yellow
and go to blue, either anti-clockwise, or clockwise? What about a ro
Not my cup of tea, but to get the ball rolling, how about "Truncated Rainbow"?
[Red, Orange, Yellow, Green, Blue, Indigo, Violet][2:]
From: Benjamin Root
To: Eric Firing
Cc: matplotlib development list
Sent: Thursday, 2 July 2015, 4:19
Subject: Re: [matplotlib-devel] Colormap survey
15 matches
Mail list logo
