One thing to note, that the backend structure will hopefully change soon
with a huge refactor of the backends.
Take a look https://github.com/matplotlib/matplotlib/pull/4143 for the
current progress and feel free to give your comments.
As a status update, I currently work on the WebAgg backend
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
Right on no longer supporting 1.5, but this code never got updated.
This is a bit of a bigger job than I first anticipated as numpy has
deprecated the norm kwarg, so we probably should too.
On Tue, Mar 10, 2015, 07:19 OceanWolf wrote:
> Tom, ``When we drop numpy 1.5''? I thought we already had
You can comment on specific lines of code in the pull request 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 a
Yes, you have almost got what I want. I know of both line comments in
the pull interface, and raising DeprecationWarnings. The problem with
the warnings that they only want to get used when you have an alternate
in place and want to remove old code soon. The problem here lies in not
knowing
Thanks OceanWolf
On Tue, Mar 10, 2015 at 3:13 PM, OceanWolf
wrote:
> One thing to note, that the backend structure will hopefully change soon
> with a huge refactor of the backends.
>
> Take a look https://github.com/matplotlib/matplotlib/pull/4143 for the
> current progress and feel free to giv
