Brénainn Woodsend

What actually is the difference in style between your two screenshots?

I've always preferred to just `--hiddenimport` VTK's submodules in as needed. They're not particularly hard to find and it's far easier to find and add missing modules than it is...

That does look like a better idea. I'll chime in there.

Nothing's changed. Just `--hiddenimport=vtkmodules.xxx` the offending submodule every time you get the `No module named vtkmodules.xxx` message.

For the reasons outlined [here](https://github.com/pyinstaller/pyinstaller-hooks-contrib/issues/327#issue-1009568297) and [here](https://github.com/pyinstaller/pyinstaller-hooks-contrib/issues/327#issuecomment-929173359).

I guess then that that leaves this issue as a hook request for pyvis so this can scoot over to the hooks repo.

`pyttsx3` has apparently been [fixed before](https://github.com/pyinstaller/pyinstaller-hooks-contrib/pull/101/commits/b3be175808ab5eb11f36ec952aea2c4010c53a02) and I see they haven't released anything new since then. Either you just need to `pip install -U pyinstaller-hooks-contrib` or our test for `pyttsx3`...

Hmm, does `--collect-submodules=pyttsx3` make any difference?

I see two ways to address this automatically and both are horrible: 1. `delvewheel` additionally modifies wheels to generate and inject a hook, add a helper to locate it then...

Hmm, I'm guessing that it was a throwaway account with no billing set up - not someone's personal key. It was added in [pyinstaller/pyinstaller#a91e12bbc488bc846d3f15eb5dbda13f285d982f](https://github.com/pyinstaller/pyinstaller/commit/a91e12bbc488bc846d3f15eb5dbda13f285d982f) which doesn't say either way.