On 21 October 2013 18:36, Chris Barker <chris.bar...@noaa.gov> wrote:
> > we can all be confident that it will work correctly.
>
> only if you've tested against the version (maybe patched) of the
> external lib they are using...
>
Of course not. We provide the framework to build mpl and run tests.
Distro developers choose how they want to build it and then run our tests.
If the tests pass then both they and us are confident that it works
correctly. We haven't had to test against anyone else's choice of library
version.
But I'm not maintaining this code, so have at it in the way that makes
> sense to you.
>
This is nothing to do with what makes sense to me; it is about following
the existing policy on C/C++ extensions when adding a new one. Just
because I am taking time to answer your questions don't presume I am taking
a particular stance. In fact I don't have a preference either way, I am
just doing the work that is required in a way that is consistent with
existing code. If there is a change of policy I am happy to do it a
different way.
Ian
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
