On Tuesday, May 18, 2021 at 3:32:23 AM UTC-5 [email protected] wrote: > They [the files in leo-editor folder] don't exist at all, if the user has installed Leo via pip from PyPI - and - not via 'git clone' from GitHub.
Somehow I never understood this. > 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 Wow. This is bad. I don't want to pick and choose which files a "more important" than others. > All / most other Python files are needed *only *for Leo's developers and *not *for Leo's users. Hmm. If possible, I would like all these files to be part all distributions. > I guess in a 'perfect' world the only Python file expected in the root folder is 'setup.py' [1]. > [1] https://packaging.python.org/ My eyes start to roll to the back of my head when I read this page :-) *Summary* I had no idea that `pip install leo` omits so many files. I'd like to fix this, but changing the locations of files could break existing scripts. 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/74d14e05-d4bd-4835-a3e9-55a0afdd6b82n%40googlegroups.com.
