Polygon examples broken

That's what I'm trying to get away from. I want to be able to write
the contains() function in patch.py and just use the normal math where
it makes sense to use normal math.

I suppose one approach is to go through all of mpl, find what is being
imported with what frequency, and build the list based on that.

Maybe I will get a chance this weekend. Right now I have to go back to
the "matplotlib svn doesn't build on windows" problem.

  - Paul

···

On Fri, Jul 20, 2007 at 02:53:42PM -0700, Christopher Barker wrote:

Paul Kienzle wrote:
> On Fri, Jul 20, 2007 at 12:34:44PM -0700, Christopher Barker wrote:
>> Out of 491 names in the numpy namespace, I found 26 that would commonly
>> be found in math expressions.

> The C99 math/complex headers define a number of symbols.

Sure, but you don't need all of those. My idea was thus:

"Namespaces are one honking great idea"

but they are kind of ugly inside math expressions. But:

"Practicality beats purity"

so I think it does make sense to bring the common names that show up in
math expressions into the main namespace. Not all the handy little names
( like isnan, zeros, linspace, etc.) only the ones that show up in the
depths of nested math expressions, so that we can write code that looks
like math. That's how I came up with my personal list of 26.

This is probably best just done by each individual according to his/her
taste.

so I think it does make sense to bring the common names that show up in math expressions into the main namespace.

This is probably best just done by each individual according to his/her taste.

That's what I'm trying to get away from. I want to be able to write
the contains() function in patch.py and just use the normal math where
it makes sense to use normal math.

Ahh -- we're back on an a mpl-devel topic now.

I was thinking that you were proposing a "math" namespace for pylab users -- but it sounds like you're proposing a standard set of math names that will be brought in to modules for the matplotlib project itself. Different issue.

I don't write enough MPL internal code to have any opinion on that.

Does anyone else think this is a good idea?

-Chris

···

--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

Chris.Barker@...236...