#1944 <https://github.com/leo-editor/leo-editor/issues/1944> suggests adding annotations for Leo's most important files.
At present, within the* ekr-annotate* branch, mypy passes all of Leo's core files without complaint, with the settings in leo-editor/.mypy.ini. Alas, many of the type annotations are redundant. The effect is a substantial *increase *in code clutter and a *decrease *in readability. Yesterday I considered writing a script that would strip off the annotations and put the annotations in stub files. But this morning I saw a simpler way... *Aha*: why bother adding and deleting annotations? Just do the type checking work in a *permanent, working* branch. So here's the plan: - As discussed in #1058 <https://github.com/leo-editor/leo-editor/issues/1058> (branch info), the ekr-annotate branch will *never* be merged into devel (or master). - Formally, the milestone for #1944 will always be the *next *release. - Any worries about future directions of type annotations will be confined to the ekr-annotate branch. *Summary* We can get the benefits of static type checking without adding type annotations to Leo's official code base. The ekr-annotate branch will be a permanent, working branch that will never be merged into devel. This branch will likely never be part of Leo's official distro. #2018 <https://github.com/leo-editor/leo-editor/issues/2018> will merge all the bugs found by mypy into devel, without all the annotations. All comments and suggestions are welcome. 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 on the web visit https://groups.google.com/d/msgid/leo-editor/fd913c7d-7e8c-463c-90e3-903b9f7e38c0n%40googlegroups.com.
