First of all, thank you very much tbp1, for answering questions regarding the installation of Leo, and to shed some light on this matter.
Now something that popped in my mind a second ago is intriguing me very much: If someone had installed Leo with pip, would then it be possible for that person to just start Leo, open leopyref.leo, hit ctrl+s, and have launchLeo.py , flake8-leo.py, launchLeo-console.py, etc. be generated in their root Leo installation folder? Thanks to anyone who answers this question! -- Félix On Thursday, May 20, 2021 at 1:39:06 PM UTC-4 [email protected] wrote: > In my view, Leo *is* a 3rd party python package and should be installable > via pip. It is true that some Linux systems will tinker with the > directories, paths, etc and want you to install certain packages using > their own package manager. But Leo as a project can't cater to all these > possible variations. > > I can see a separate pip package named, say, "leo-server" or some such > that includes the parts that you want to work with that ordinary users > can't. Such a package could I'm sure be created by a script that creates a > temporary directory tree with the extra parts for the packager to package > up. Or maybe the existing setup.py can be enhanced to do that. > > On Thursday, May 20, 2021 at 1:29:26 PM UTC-4 Félix wrote: > >> What happened to the standard 'installer' program concept... >> "install.msi" or .exe. or whatever? Is that still a thing? >> >> Leo is not a python library like 'websockets' or some other 3rd party >> functionality library... should it not be installed with a 'real' >> installation program? (on windows) and some .deb package on debian linuxes, >> etc...? >> >> I'm a newbie with regards to those things... Just asking for my own >> curiosity for whomever has answers to this to answer back, if any... :) >> -- >> Félix >> >> On Thursday, May 20, 2021 at 8:56:23 AM UTC-4 Edward K. Ream wrote: >> >>> 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/eb1e9621-9f9d-45f6-be94-7defe3f3f81cn%40googlegroups.com.
