On Mon, 27 Nov 2017 06:07:13 -0600 "Edward K. Ream" <edream...@gmail.com> wrote:
> On Sun, Nov 26, 2017 at 3:02 PM, <rvn...@tesco.net> 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-install). > > What, exactly, is a "standard python install"? It's something of a non-question, seeing even though Python has "standard" methods, each platform also has package management options, and different users will tend to use Python centric or platform centric methods. That said, I would say setup.py and pip tie for Python's standard installation pathway. > Imo, using Anaconda will save most users a lot of aggravation in the > long run. IPython recommends this approach, and I agree. A few > extra minutes of download time will repay themselves many times over. > On modern machines, the extra space requirements don't matter. Telling people they need to install Anaconda to run Leo will put people off trying Leo. It's almost as bad as telling them they need to use git to get Leo ;-) - Anaconda can appear, at first glance, to be commercial - Having to install a large (500 Mb) framework to run Leo implies (incorrectly) that Leo is not a whole thing by itself - Users then need to work out how to use Anaconda to manage dependencies - if Leo is an app., how is managing dependencies even a thing? - All Python systems (including Anaconda) integrate with pip, so even experienced Python developers who have chosen a stack other than Anaconda (the scientific analysis distro.) for domain specific reasons may lose interest if they're told you have to use Anaconda and can't use pip. 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. I think it comes down to what filter we're trying to apply to incoming users. Python devs only? Or all comers, even writers ;-) Matt's pip install seems to get Leo running with minimal effort, as long as you use Python 3. I'm not sure what it does currently, but hopefully it can report the things your missing because pip can't find them for your OS, maybe even point to (mini)Anaconda instructions on Leo's web site as a fuller alternative. But the important thing is that it gets Leo running so the user has a chance to see it rather than just drifting on to something that's easier to install. Spelling and formatting rst aren't critical to demoing Leo - Leo should start with nothing more than PyQt, as far as I'm aware. Cheers -Terry > Please do not burden Leo's devs with issues relating to a user's > unwillingness or inability to install dependencies. I'm not going to > have a lot of sympathy for such troubles. > > Having said that, if a plugin fails to load due to missing > dependency, it should clearly report that fact. > > 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
