Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


Sorry for the incomplete links!

  
http://stackoverflow.com/questions/15223209/installing-pyuno-libreoffice-for-private-python-build#28593413

  http://askubuntu.com/questions/488529/pyvenv-3-4-error-returned-non-zero-exit-status-1
  http://askubuntu.com/questions/412178/how-to-install-pip-for-python-3-in-ubuntu-12-04-lts


On Thu, Feb 19, 2015 at 05:45:58AM +0100, Jens Tröger wrote:
Hello,

The question in this email arose from Stephan Bergman's answer to a
stackoverflow thread:

  http://stackoverflow.com/questions/15223209/installing-pyuno-libreoffice-for-p

What is the proper and recommended way of building a Python virtual
environment around the LO Python?  I'd like to ensure that uno is
available and functioning, while at the same time I can install
additional packages into the venv?

Also, I just noticed that on Ubuntu (nor Gentoo) there isn't even a
Python interpreter, in spite of installing the script provider package.
On Mac, there is.

There seem to be various ways of going about this, for example:
  
  http://askubuntu.com/questions/488529/pyvenv-3-4-error-returned-non-zero-exit-
  http://askubuntu.com/questions/412178/how-to-install-pip-for-python-3-in-ubunt

Unfortunately, I didn't find that documented on the LO site.  Or did I
miss something?  I'm somewhat unclear on this whole issue...

Cheers :)
Jens

-- 
Jens Tröger
http://savage.light-speed.de/

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.