Thanks PhilC, it's a bit of a struggle to match versions of inter-dependent modules, but I finally got to the point of importing SciPy and NumPy modules that will play nicely together. (If I just imported the latest scipy, numpy complained it was an older version and spat the dummy.)

Despite playing with .pth files and adding entries to the sys.path to try and force Poser to find a replacement numpy module before its own (within the app's site-packages directory), I ended up having to rename the Poser numpy directory to oldnumpy and then it happily (and silently) discovered the more recent version of numpy where I'd been telling it to look. I suspect that Poser's own internals might be hardwired to reference the "built-in" numpy, and unless you pull the plug on it, it won't find another numpy even if it's parent directory appears earlier in sys.path.

Of course, when I have to report a Poser bu## er, feature, I'll have to back out the oldnumpy change. :-/

---

My ShareCG Stuff

Verbosity: Profusely promulgating Graham's number epics of complete and utter verbiage by the metric monkey barrel.