On Oct 24, 2013 8:40 PM, "Chris Barker" <chris.bar...@noaa.gov> wrote:
>
> On Thu, Oct 24, 2013 at 8:29 AM, Michael Droettboom <md...@stsci.edu>
wrote:
> > Here are the notes with action items from the meeting:
>
> thanks for posting that. I see:
>
> pylab - should it stay or should it go?
>
> Comment from the peanut gallery:
>
> Go.
I agree, but that leads to another question: go where?
Some of the stuff there is clearly redundant and should be removed entirely.
Others I think are functionality that should be merged into numpy, although
whether they would agree I don't know.
Others are useful but I don't know exactly where they could end up.
I think we need to go through on a case-by-case basis and figure out what
to do with each class and function.
I think it would probably be good to do something similar with cbook. Both
are dumping grounds for largely unrelated functions. At the very least they
should be organized into modules by their purpose, but I do think some
should be dropped or upstreamed.
------------------------------------------------------------------------------
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
