I'm only a sometime Linux user, so take comments below with that in mind. - if user have root access and want to make leo available for all users >
"sudo pip install ..." should work to install modules globally, and "pip install --user ..." for just current user. I understand there may be issues resulting from "sudo pip" to manage system packages instead of the system package manager (apt-get, rpm, yum), but that shouldn't be a problem with Leo as the only extra requirement (possibly) pulled by pip is docutils(?). - if user want development or stable version : > Pypi will (probably) only hold stable versions. So "pip install leo" should always grab a stable version. "pip install --pre leo" has been used in the last couple of weeks, but only for testing for the stable release. I would recommend always using "pip install https://github..."; for development versions. It gives the most flexibility for choosing which dev version (any commit or branch or tag), and invokes no overhead at all on package managers. > - if user can and want to install it with pip as a python package or in a > more "standalone" way > not sure what is meant here. > - if user want a desktop integration > This is the point where pip doesn't help. It's possible to address with included scripts, but no one's written those yet. It would be a good enhancement issue for the tracker. -matt -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
