Usecenter could probably go, although it hasn't even been tested yet.  :-P  Mixboxes would be an option for localspace runs, yes.  I like to keep options open, to the point of cluttering things a bit....  (I learn, gradaully, to trim, however; I made no plans to try to introduce any kind of x-symmetry function, after it proved a hassle in the earler vert-to-vert version....)  I haven't been using it, but mixboxes was sort of central to one of the ideas I mentioned above.

The idea behind the Numeric.equal code was really that I was wondering if your vector_equal might run better before sending anything to the bounds check.  My early tests suggested that the edge bounds check was the source of most of the RAM leaking, and I've tended to want to avoid it as much as possible, since then....

Numeric runs off the compiled numpy.dll, so apparently there are speed gains to be had there.  All of this would be faster in a compiled language, I assume.  I'll hold off on Numeric tweaks, then.  It's become my new toy, after having been initially frightened of it.  :)

The response editor is mangling my posts again.  My apolgies for any garbled bits.

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.