Possible next project for me

[Edward K. Ream]

This morning I had what I sometimes think as an Aha/Doh moment :-) The background:

- I've often said that creativity happens only in the presence of a juicy problem.

- Leo is a tool for understanding complex programs.

Putting these two together: the way forward may involve studying complex python programs and seeing what new tools/inventions result.

pylint and mypy are immensely complex programs, so studying them will surely call forth new tools.

Summary

Finding new ways of understanding mypy and pylint seems like a juicy project.  But perhaps an even juicier project may appear :-)

Edward

[tbp1...@gmail.com]

You could look at Reportlab or Pillow ...

[zhaohe wang]

@Edward Yes I agree with you. I wrote a blog which using leo-editor to analyse flutter pugin named fluro offical example. 

Here is the blog, but written by Chinese. I want to share some leo-editor usage experience.

https://blog.csdn.net/weixin_42553238/article/details/121447509

fluro example: https://github.com/lukepighetti/fluro/tree/main/example

I think that users who using leo-editor can read source code as a literal article.  They should not jump here then jump there again and again.