Hello Félix Félix schrieb am Dienstag, 18. Mai 2021 um 00:55:18 UTC+2:
> > I don't know much at all about those python system specific issues. > (although I wonder how the other python files that import parts of leo do > exist in the root of the leo folder without problem, such as launchleo.py, > ect.. ) > My answer to your question is: They don't exist at all, if the user has installed Leo via pip from PyPI - and - not via 'git clone' from GitHub. I guess this is not / has not been considered a major issue, because if users are developing plugins for Leo - or - are contributing to Leo itself, it's assumed that they work in their own local repository cloned from GitHub anyway. The problem / surprise occurs for *any *user, which is assuming that both installation methods provide equal functionality. List of Python files in Leo's root folder: * flake8-leo.py * launchLeo.py -> similar functionality is available in .../leo/scripts/leo , leo.bat , etc. ! * launchLeo-console.py * leoclient.py * leoserver.py * profileLeo.py * pyflakes-leo.py * pylint-leo.py * run_pytest_test.py * run_travis_unit_tests.py * setup.py All / most other Python files are needed *only *for Leo's developers and *not *for Leo's users. I guess in a 'perfect' world the only Python file expected in the root folder is 'setup.py' [1]. I'm not an expert on this topic - so - my explanation / view may not be entirely correct. With kind regards, Viktor --- [1] https://packaging.python.org/ -- 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/85596d8c-3a87-4b1f-901c-26b5854fcc63n%40googlegroups.com.
