Kay Hayen

Part of the 2.3 release.

I am assuming I will need yaml config for this one too, right?

Seems this is what is needed: ``` - module-name: 'aspose.email' dlls: - from_filenames: prefixes: - 'email' - 'pycore' - 'pygc' - 'pyreflection' suffixes: - 'pyd' when: 'win32' - from_filenames: relative_path:...

That looks horribly wrong: ``` - module-name: 'aspose.email' dlls: - from_filenames: prefixes: - 'email' - 'pycore' - 'pygc' - 'pyreflection' suffixes: - 'pyd' when: 'win32' ``` Given that `email` is...

That's how these seem to be done correctly, not getting all you had there: ``` - module-name: 'aspose.email' implicit-imports: - depends: - 'aspose.pyreflection' - 'aspose.pygc' ``` DLLs with "pyd" suffix...

My hopes have been shattered though, it seems the issue persists, email is both a directory and an extension module, I was thinking that might play a role.

So, I found the probably bad thing: ``` foreach_file(AsposeModuleLoader.aspose_native_lib_dir, _platform_suffixes, lambda name, path: __all__.append(name)) sys.meta_path.append(AsposeModuleFinder()) ```

I don't know if this is doable, they have their own source file loader, as as meta path based loader, and I guess, aspose.email is supposed to be loaded by...

Turns out, it is doable, since we can let their code do the extension module loading, and there is no Python code in there, so whatever it is that they...

It seems, my backport to 2.0.4 hotfix has failed, that's not going to work, unless I split it up into a unoptimal part, where all Python versions extension modules are...