NumPy vs. iterative vs. ???

[Tim Lavoie]

In article <m2aeduerjz.fsf at spiff.home.com>, Tim Hochberg wrote:
>tim.lavoie at mts.net (Tim Lavoie) writes:
>
>Fun!
>
>I played around with your code and came up with the attached. It's
>about twice as fast by pruning the set of points to look at each
>iteration, but no longer returns the full arrays of c and z. (I think
>that could be added back in if nescessary). I agree that NumPy may not
>be the most elegant way to attack this kind of problem, but it's
>probably as good as your going to get from within Python.


Neat!  I'll play with this a bit, so I can work through the logic a bit.
Being a NumPy newbie (Numbie?), it's all a bit odd still. I'd still want to
keep the z and c data, since I want them for alternative coloring methods.
If you've seen a program called fract-o-rama, you'll see what I mean. 
Here's a URL:  http://locutus.kingwoodcable.com/jfd/fractal/

Basically, I like what it does, but I have some of my own ideas about how
I'd like to do stuff.