Are you suggesting a reorganization of the Geom module?  We could organize things by vertex and polygon, instead of using generalized geometry lists.  Would there be a memory savings if we had a vertex class instance for each vertex and a polygon class instance for each polygon?  Wouldn't defining a new type be creating a class container for the data, essentially?  Or is there more to it?  I guess I should read the Python docs, huh?

Ah.  There is more to a type.  That involves building something in C, eh?

One of the Python packages for graphics handling might have something, but if we create a dependency to an external package, there are installation hassles for the end user, and the risk that the package might cease to be available at some point, or change and come into conflict with our use of it....

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