Hi,

On 21/03/17 09:11, Edward K. Ream wrote:
On Mon, Mar 20, 2017 at 7:00 PM, Offray Vladimir Luna Cárdenas <[email protected] <mailto:[email protected]>> wrote:

    I like how documentation is getting more compact and direct.

​I agree. This is a big step forward, for everyone, but especially for first timers.​

    I wonder if installation instructions could go from the most
    newbie friendly to the not so newbie ones (maybe after releasing
    5.5). So installation should start from the most common used
    installation method of the intended platform and then go to more
    powerful ones.

​Heh. The eternal tension. Perhaps you could have a conversation with Lewis Neal.​

If the miniconda method progress, Lewis could help in creating the yaml manifest for Mac, instead of the brew installer... I started thinking in this, installation method, but as the mail progressed miniconda seems

    ​... ​
    I was wondering how Python related projects do this nowadays. One
    path is Conda and, particularly, Miniconda which manages
    dependencies and is already packaged for several platforms [1],
    but seems that a full installation can be overkill for Leo and its
    prerequisites
    ​​
    [2].

​Overkill, maybe, but I think it is useful overkill. Installing the full Anaconda package (or packages, if you install for both Python 2 and 3) saves a lot of time in the long run. I'm not looking for anything better. Besides, these days even small machines typically have huge memories.​

Yes. I will start with miniconda and see what we can bootstrap from there. Connectivity is not the same in the Global South and Leo has users in India and Colombia. Reducing the amount of stuff you have to download to start with Leo is important to make it global.

    In the Jupyter case the map they provide [3] gives the user and
    overview of what they want to do, based on the answer the user
    gives to a question, and they use the external installer method
    (in their case Anaconda) to the final installation, making it
    pretty easy [4] ('cause the heavy work is done by conda and not
    the user/developer). Conda can be also used to upgrade the
    software, including updating/building from git[5]

​I think this is just fine or Leo too.


I agree. I will try miniconda for my python related stuff (is not much these days) and try to give feedback.

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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to