Why does NVDA use comInterfaces instead of the default comtypes.gen path?

[gexgd0419]

Although comtypes.gen supports customizing gen_dir to change the directory for the generated wrapper modules, the generated modules themselves still import from comtypes.gen, which can cause some trouble for static type checkers, as the modules are not actually in comtypes.gen.

NVDA tries to address this issue by modifying the comtypes generated code, but this can break when comtypes changes the generated code again.

I asked the comtypes folks about it, and they said that most people already use the default comtypes/gen path without problems.

So why did NVDA choose its own path? What's the advantage of it, despite requiring some hacks to make it work?

[seanbudd]

There's no known documented reason, it's probably fine