On Sunday, November 23, 2025 at 1:44:08 PM UTC-6 Edward K. Ream wrote: My next step will be to adapt Leo's python importer so that it copies signatures for classes, methods and functions into a .pyi (stub) file.
That would be a big mistake--discovering function signatures is but a small part of the problem. Instead, the next step will be to play with mypy's stubgen <https://mypy.readthedocs.io/en/stable/stubgen.html> script. I've just spent 15 minutes studying it. It's based on a full analysis of the ast (parse tree) as it must be. The following appears at the end of the module-level docstring: "Note: The generated stubs should be verified manually." A Leo-specific tool *must* rely on the generated stubs *without any manual changes*. The whole project will fail if not, even after adding various Leo-specific hacks. We shall see. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/leo-editor/74c792cf-ee38-474b-a4a7-81be02ba31b2n%40googlegroups.com.
