>
> To make it safer use a different ~/.leo for each one by changing HOME
>> environment variable before starting Leo.
>>
>
> *This is counter intuitive to my understanding of why Python has
> introduced PyVE's!*
>
> At the moment my gut feeling is that Leo should change here ...
>
It becomes
I am going to reiterate here something I posted in another thread. If you
want to use the git method (or indeed run from a downloaded unzipped
archive), there is another way to set up your system besides virtual
environments or pip install --editable. I do it this way because I have
the
> As the footnoted reference says, If you install from Git, you can get the
> latest development versions. What it does not say is that the latest
> development version is usually not in the "master" branch of the git
> repository. It is usually in the "devel" branch.
>
Good point, I
On Saturday, April 25, 2020 at 2:50:25 PM UTC-4, Viktor Ransmayr wrote:
>
> Hello Matt,
>
> This is a first response from my side, in order to provide you an
> **initial** feedback!
>
> In other words, I might change my mind, if I wake up tomorrow morning -
> and - will review this thread /
>
> The installing instructions Edward linked to look complicated because
>> they're long, but really it just boils down to:
>>
>>- install python (v3.6 or newer)
>>- run: pip install leo from a python enabled command prompt
>>- run leo from that same python enabled command prompt
>>
As the footnoted reference says, If you install from Git, you can get the
latest development versions. What it does not say is that the latest
development version is usually not in the "master" branch of the git
repository. It is usually in the "devel" branch. If you don't know Git a
bit -
On Tuesday, April 21, 2020 at 3:56:26 PM UTC+2, Edward K. Ream wrote:
>
> >Associating code with unit tests would be useful, but putting tests
> in p.u is about the most complicated thing that might work.
>
Of course. Conceptually, AFAICT, unit tests and code are in a similar
relation as
Hello Matt,
This is a first response from my side, in order to provide you an
**initial** feedback!
In other words, I might change my mind, if I wake up tomorrow morning - and
- will review this thread / topic again ;-)
Am Sa., 25. Apr. 2020 um 20:16 Uhr schrieb Matt Wilkie :
>
>>
>> *can not
Hello Matt,
Thanks for this explanation!
Am Sa., 25. Apr. 2020 um 20:27 Uhr schrieb Matt Wilkie :
> Why should I prefer this method, if I don't get anything else than if I
>> would simple do a 'pip install leo'? - What am I missing?
>>
>
>- Upgrades are faster and easier, a simple `git
Hello Matt,
Am Sa., 25. Apr. 2020 um 19:46 Uhr schrieb Matt Wilkie :
>
> I'm sorry to say that we lost the ability to easily build an all-in-one
> exe. It's on my list of things to get to again but aren't there yet (and
> not likely to be soon). That said, installing it the techy or developer
>
> Why should I prefer this method, if I don't get anything else than if I
> would simple do a 'pip install leo'? - What am I missing?
>
- Upgrades are faster and easier, a simple `git pull` and you're done.
Only the new and changed files are downloaded. With a pip upgrade a full
Hi Viktor,
>
> *can not open
> /home/user/PyVE/PyPI/Leo-stable/lib64/python3.7/site-packages/setup.pynot
> found:
> /home/user/PyVE/PyPI/Leo-stable/lib64/python3.7/site-packages/leo_to_html.xsl*
>
[...]
*Pypi installed Leo *doesn't have the files which are in the root directory
of the
Hi Matelot,
I'm sorry to say that we lost the ability to easily build an all-in-one
exe. It's on my list of things to get to again but aren't there yet (and
not likely to be soon). That said, installing it the techy or developer way
is much easier than it used to be.
The installing
Hello Edward & Community,
As I stated in my other message (
https://groups.google.com/d/msg/leo-editor/gNXPxjD9Yvg/z4bW4CtNAwAJ ) I now
have successfully created a third PyVE, where I followed the method
described in [1].
What's surprising to me - and - I'm taking the view of a Leo newbie
Hello Edward & Community,
Am Samstag, 25. April 2020 14:50:03 UTC+2 schrieb Viktor Ransmayr:
>
>
> I'm trying to understand the various installation options mentioned in
> Leo's documentation better.
>
> As you know from my previous post, I almost always rely on the latest
> released stable
I've done it from time to time, sometimes by accident. Each instance of
Leo will use the same configuration files, as your logs show. This means
that the last instance to exit will be the one that may change these files,
like the list of recent files.
I have also noticed that if I have the
Hello Edward & Community,
I'm trying to understand the various installation options mentioned in
Leo's documentation better.
As you know from my previous post, I almost always rely on the latest
released stable version of Leo installed via pip from PyPI into a dedicated
PyVE.
Today I tried
On Sat, Apr 25, 2020 at 12:03 AM matelot wrote:
> Windows:
> I run Leo by starting this via powershell: ...\
> Leo-5-5_Win\LeoAppFolder\LeoApp.exe
>
> Now I have a new PC, where can I download the latest ?
>
Leo no longer exists as a stand-alone .exe file. Otoh, `pip install leo`
should work.
On Fri, Apr 24, 2020 at 9:28 PM Thomas Passin wrote:
Glory Be! The external Python file I sent you imported like a charm.
> Cruising through it, it seems to be in order. Thanks!
>
You're welcome. Thanks for the confirmation. I'll close #1581 when the
import code handles section references.
19 matches
Mail list logo
