Jun Komoda
                                            Jun Komoda
                                        
                                    @rafikor > But when GetModule is called with absolute path of *.tlb file, then the error does not occur. It is strange for me, I thougth that processing of *.tlb...
@rafikor Thank you for your investigation. It seems to me that it would be reasonable to ensure that `CreateObject(prog_id_str)` returns object and generates a module equivalent to the code generated...
@rafikor > Maybe you know places in comtypes where some code specific to platform is located (like, e.g., definition of whether called application is x86 or x64 according to the...
@vasily-v-ryabov Thanks for your response. I am not very familiar with c-ffi or the c language itself. I'm trying to learn, but for me, adding type hints to this package...
@karpierz I am restoring some tests in `comtypes`. I am trying to restore [`test_excel.py`](https://github.com/enthought/comtypes/blob/fbc7cf5d3597d78f661bd0f3799f58b69f62a85e/comtypes/test/test_excel.py)(currently skipped because it depends on specific environment, see https://github.com/enthought/comtypes/pull/298#issue-1264854040), and I was trying to use `unittest.skipIf`...
@bennyrowland Your `test.tlb` example may help me solve #303 at the same time. I am also trying to figure out how to solve this problem, so if I come up...
@bennyrowland I don't know much about c-pointers, so I may be guessing, but I thought a double or more pointer might solve the problem. In terms of the code generated...
A long time has passed since this issue was posted. And now, - [`comtypes==1.1.11`](https://github.com/enthought/comtypes/releases/tag/1.1.11) has been released and is coded Python3 native. - while still being backward compatible to 2.7...
@vasily-v-ryabov I agree with your suggestion to support only Py 3.6+ when dropping Py 2.7. With Py3.6+, we can use the built-in `typing`. And `enum` module is also supported, which...
@vasily-v-ryabov I think the problem reported in this issue has been resolved in 1.1.13. I think this issue should be closed.