--
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 leo-editor+unsubscribe@googlegroups.com.
To post to this group, send email to leo-e...@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
2. Install the prerequisites for Leo. These I usually install using pip or the package manager in the distribution. Try pip first.docutils, pandoc, pyxml, pyenchant, git
--
With regard to dependencies, do you recall what docutils, pyxml, and pyenchant required for? I don't have them in my list, but haven't
seen any errors about them either.
I think that the suggested method of installing anaconda is not the optimal way to facilitate this;
5) a setup.py is the standard way of installing a python program and used by distribution-specific install-scripts that enable keeping track of what is installed. Pip makes this more obscure so that it is important that a setup.py file is present and up-to-date
What is important is that configuration on a linux system can become more straightforward than it currently is, that is via use of the leoSettings.
On Sun, Nov 26, 2017 at 12:56 PM, <rvn...@tesco.net> wrote:
5) a setup.py is the standard way of installing a python program and used by distribution-specific install-scripts that enable keeping track of what is installed. Pip makes this more obscure so that it is important that a setup.py file is present and up-to-dateLeo is an app, not a python package. I would like to see setup.py disappear completely. Perhaps Matt has already done that as a result of his work creating a linux package.
Hi,
Anaconda can be overkill for installing Leo, but Miniconda is no (only 60 mb). It's the preferred way those days to give installing support in the Python (scientific) ecosystem, and making Leo conda installable is important for the same reasons that Jupyter, Numpy and all the other packages in that ecosystem have chosen coda: to make installation easier and more modular and let you experiment without system specific installs that preclude parallel versions and sandboxing and are distro/OS specific.
So a good install procedure for Leo could be:
- Install *miniconda* (60 mb).
- conda install leo.
A template of how this is done in Jupyter is here:
https://cs205uiuc.github.io/guidebook/resources/python-miniconda.html
Cheers,
Offray
--
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 leo-editor+...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscribe@googlegroups.com.
To post to this group, send email to leo-e...@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
--
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 leo-editor+unsubscribe@googlegroups.com.
I not a programmer either. Installing Miniconda is the same effort as installing Anaconda, gives you the same core functionality (with less overheat and preinstalled packages, mostly for science) and it saves bandwidth, space *and* time, which is handy in places in the Global South, where bandwidth is not cheap and/or reliable.
So, installing Miniconda just works also and keeps things light
so users can focus in their tasks with Leo, instead of fighting
dependencies or distro/OS specific idiosyncrasies.
Cheers,
Offray
To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+...@googlegroups.com.
Leo is an app, not a python package.
Leo is an app, not a python package.Well I do not think this is a relevant difference; all pip-installs end in python/site-packages. And most setup.py installs as well.