Okay.  Two questions.

1. Is it bad to have an option to fill verts with the localspace vertex coordinates?  These are sometimes useful, or even necessary (as when creating a morph which doesn't bake in the worldspace positions).

2. Is there any reason not to allow vpolys for tris, or is that simply not added?  I've had cases where the vpolys list for... tpolys, as you call it, has been useful.

I'm really pleased to see the distance functions ported over.  I was considering using squared distances for something, recently, because I was afraid the square roots would slow things. 

You know... I don't know this.  What does the abs function do when applied to a vector?  Just return the abs value of all the vector values?  Or is it completely different?

===========================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.