Thanks Viktor. This is a known issue, but yet to be documented up front where people see it. Basically anything in the root folder of the leo-editor code repository is not installed when using pip. This is because they need to be relative to `./leo-editor/leo` folder, which make them at the top of `./site-packages`, and thus in the global namespace and not part of leo (as far as python is concerned).
Before (source code repository view): leo-editor/leo/* # <-- this is actually Leo leo-editor/pyflakes-leo.py # <-- this is an extra After (pip installed): .../site-packages/leo/* # <-- this is actually Leo One solution is to restructure the whole repository into what's called the "src layout" (https://blog.ionelmc.ro/2014/05/25/python-packaging/). That's a big change. Alternatively we could move pyflakes and friends into a `./leo/tools` subfolder. That's a smaller change, but I don't know how it would impact workflow of the people who use them; the change might not be small to them. The decision last week was that people who use LeoPyRef would/should be working with the complete development environment, either from a `git clone {url} && pip install --editable {path}` or `pip --editable {url}`. The thinking being that only people wanting to hack on Leo would be interested in the file. Maybe that's not always true(?) Matt -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
