On 28/11/17 09:57, Matt Wilkie wrote:
> From bare Python 2 install, linux (debian and kin):
>
> apt install python-pyqt5
> pip install leo
>
In Arch/Manjaro and alike:
yaourt -S leo
That's it. But (Ana/mini)conda would provide a distro/OS neutral single
way to install/update the softwa
thanks for the extended background/justification Terry :)
> Matt's pip install seems to get Leo running with minimal effort, as long
as you use Python 3.
They common configurations are minimal, they just aren't all wrapped up in
a single simple instruction set:
>From bare Python 3 install, wind
Hi,
On 27/11/17 09:17, Terry Brown wrote:
> Miniconda only partly mitigates these drawbacks.
>
> I'm not saying that Anaconda / Miniconda shouldn't be suggested *among*
> the options, they just shouldn't be presented as the only option,
> just as getting Leo from git shouldn't be the only option.
On Mon, Nov 27, 2017 at 8:17 AM, Terry Brown wrote:
I'm not saying that Anaconda / Miniconda shouldn't be suggested *among*
> the options, they just shouldn't be presented as the only option,
> just as getting Leo from git shouldn't be the only option.
>
Perfectly reasonable.
I think it comes
On Mon, 27 Nov 2017 06:07:13 -0600
"Edward K. Ream" wrote:
> On Sun, Nov 26, 2017 at 3:02 PM, wrote:
>
> > My 2 cents: the only dependencies that needed to be reported are
> > modules needed to run Leo on a standard python install.
> > Thus, in my view, Leo should present itself with a set of p
On Sun, Nov 26, 2017 at 3:02 PM, wrote:
> My 2 cents: the only dependencies that needed to be reported are modules
> needed to run Leo on a standard python install.
> Thus, in my view, Leo should present itself with a set of plugins that
> will work out of the box (i.e. on a standard python/os-in
My 2 cents: the only dependencies that needed to be reported are modules
needed to run Leo on a standard python install.
Thus, in my view, Leo should present itself with a set of plugins that will
work out of the box (i.e. on a standard python/os-install).
Any other dependencies that come in by
On Thu, Nov 23, 2017 at 10:50 AM, vitalije wrote:
> But it's a bug if viewrendered won't load without it, as rst doesn't need
>> to be rendered to be useful, and viewrendered should show it in its raw
>> form. I think the rst is displayed in the log as a fallback, which is ok.
>
> Here is viewre
Status update: we're down to only docutils as a reliable pip-installable
dependency:
- pyenchant - no wheels for some platforms, e.g. amd64
- pyxml - no pip package
- PyQt5 - only py3 (but is reliable there)
- python-qt5 - for py2.7, only available for Windows, but not reliable
beca
Hello Terry & Leo-Community,
2017-11-23 16:19 GMT+01:00 Terry Brown :
> On Thu, 23 Nov 2017 00:20:34 -0600
> "Edward K. Ream" wrote:
>
...
> Indeed. The way to cut through all this morass is to use the
> > Anaconda distribution. This gives you almost everything you ever
> > need, except pyl
>
> But it's a bug if viewrendered won't load without it, as rst doesn't need
> to be rendered to be useful, and viewrendered should show it in its raw
> form. I think the rst is displayed in the log as a fallback, which is ok.
Here is viewrendered init function. Clearly it refuses to start w
On Thu, 23 Nov 2017 05:51:25 -0800 (PST)
Josef wrote:
> It seems to me that docutils is even required for the viewrendered
> plugin (perhaps indirectly?)
viewrendered uses docutils to render rst (reStructuredText) formatted
docs. But it's a bug if viewrendered won't load without it, as rst
does
On Thu, 23 Nov 2017 00:20:34 -0600
"Edward K. Ream" wrote:
> On Wed, Nov 22, 2017 at 6:20 PM, Terry Brown
> wrote:
>
> > markdown.py would be a much lighter dependency than pandoc,
> > although a bit less featurefull. My goal is to have leo_edit_pane
> > replace viewrendered. LEP will use eithe
It seems to me that docutils is even required for the viewrendered plugin
(perhaps indirectly?)
>
> es = {'develop':[
> 'pylint','pyflakes', # coding syntax standards
> 'pypandoc', # doc format conversion
> 'twine','wheel','keyring' # Pip packaging, uploading to PyPi
> ]}
> ~~~
>
> You probably take this in to account already, but a lot of these things
>> are "recommends" rather than "requires" kind of dependencies.
>>
>
> Indeed. The way to cut through all this morass is to use the Anaconda
> distribution. This gives you almost everything you ever need, except
> pylint.
On Wed, Nov 22, 2017 at 6:20 PM, Terry Brown wrote:
> markdown.py would be a much lighter dependency than pandoc, although a
> bit less featurefull. My goal is to have leo_edit_pane replace
> viewrendered. LEP will use either.
>
> You probably take this in to account already, but a lot of these t
thanks!
pypandoc is a wrapper around the pandoc commandline utility, allowing a
person to use pandoc from within python using python style syntax. It's a
sledgehammer solution to the small hammer problem I faced converting Leo's
markdown readme to restructured text for Pypi.org. However pandoc is
markdown.py would be a much lighter dependency than pandoc, although a bit less
featurefull. My goal is to have leo_edit_pane replace viewrendered. LEP will
use either.
You probably take this in to account already, but a lot of these things are
"recommends" rather than "requires" kind of depen
pyxml is required if you want to import xml files.
pandoc is required for users if they wish to view markdown files using
viewrendered. I am not sure of the difference between pandoc and pypandoc.
Chris
On Wed, Nov 22, 2017 at 12:34 PM, Matt Wilkie wrote:
> I'm in the closing stretch for Iss
I'm in the closing stretch for Issue #586, separating end user dependencies
from developer requirements. This is what I have now, is anything missing?
~~~
user_requires = [
'docutils', # Sphinx, rST plugin
'pyxml', # ?
'pyenchant', # spell check support
'PyQt5; python_version >= "3
20 matches
Mail list logo
