Parmatic is a package - so yes it is the name of a folder and has an init.py for its main module.

Parmatic made the assumption that Poser could always be expected to place its main runtime/Python folder into sys.path. Apparently PP2012 doesn't do that, eh?

I learned my lesson after that and you can see that matmatic is more clever. I had so many problems with Mac versus PC paths that I gave up on making any assumptions other than you would keep the matmatic files together in a matmatic package, and that I could find said folder and set it up in sys.path because you would be running one of the files included in the package.

You could update parmatic to do the same trick if you like. I put parmatic in the public domain, if I recall correctly.

Oh - and I used from X import Y on purpose. Doing otherwise risks picking up a module from elsewhere, although I have to admit that I used belt and suspenders. It is incredibly unlikely to accidentally pick up somebody else's module when its name has the word parmatic in it. But technically speaking, a naked "import ParmaticActor" is semantically different than "from parmatic import ParmaticActor". Particularly when "ParmticActor" could be the name of a function, versus a module, the longer form is necessary.

 

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)