matplotlib-devel Mailing List for matplotlib

Thanks OceanWolf

On Tue, Mar 10, 2015 at 3:13 PM, OceanWolf <jui...@ya...>
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 give your comments.
>
> As a status update, I currently work on the WebAgg backend (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
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

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 how long the life-cycle will last for an indeterminate amount of 
time, such as numpy-1.5 here, or python-2.7.  Lots of such items can 
stack up, and easily get forgotten about, as we see here.

On 10/03/15 17:12, Paul Hobson wrote:
> 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 at 8:51 AM OceanWolf 
> <jui...@ya... <mailto:jui...@ya...>> 
> wrote:
>
>     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 github would add that as a feature if asked?
>
>     ------------------------------------------------------------------------------
>     Dive into the World of Parallel Programming The Go Parallel
>     Website, sponsored
>     by Intel and developed in partnership with Slashdot Media, is your
>     hub for all
>     things parallel software development, from weekly thought
>     leadership blogs to
>     news, videos, case studies, tutorials and more. Take a look and
>     join the
>     conversation now. http://goparallel.sourceforge.net/
>     _______________________________________________
>     Matplotlib-devel mailing list
>     Mat...@li...
>     <mailto:Mat...@li...>
>     https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

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 at 8:51 AM OceanWolf <jui...@ya...>
wrote:

> 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 github would add that as a feature if asked?
>
> ------------------------------------------------------------
> ------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

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 github would add that as a feature if asked?

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 <jui...@ya...> wrote:

> 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 calculate the
> normalisation parameters first, and then apply those parameters on
> subsequent plots.
>
> To ease the user, we could add a method to return the binning parameters
> from a single binning exercise, and then give an option to pass those
> params in to subsequent plots.
>
> ------------------------------------------------------------
> ------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

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 calculate the 
normalisation parameters first, and then apply those parameters on 
subsequent plots.

To ease the user, we could add a method to return the binning parameters 
from a single binning exercise, and then give an option to pass those 
params in to subsequent plots.

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 (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