z3c.recipe.openoffice
This recipe download openoffice in your buildout, it can also (optional) create egg with pyuno and change the default python used by openoffice.
More info about Python UNO: http://udk.openoffice.org/python/python-bridge.html
We are using this to generate OpenOffice documents from zope/python
Buildout configuration:
Add this section to your buildout configuration:
[buildout] parts = ... your other parts ... openoffice ... [openoffice] recipe = z3c.recipe.openofficeThis will just download and install openoffice in your buildout
To create the pyuno egg add the fallowing config:
[openoffice] recipe = z3c.recipe.openoffice install-pyuno-egg = yesTo also change openoffice python, add the following config:
[openoffice] recipe = z3c.recipe.openoffice install-pyuno-egg = yes hack-openoffice-python = yesBy default it will fetch version OpenOffice 2.3 but you might want to install from another location or another version like this:
[openoffice] recipe = z3c.recipe.openoffice install-pyuno-egg = yes hack-openoffice-python = yes version = 2.3.1 download-url = ftp://ftp.openoffice.skynet.be/pub/ftp.openoffice.org/stable/2.3.1/OOo_2.3.1_LinuxIntel_install_en-US.tar.gz
Notes:
For this to work an OpenOffice process need to be running in background. As this require a X server and you don’t want to install a real X server in a production environment you might want to use Xvfb. Here are the lines we use to start openoffice:
$ cd myBuildout $ Xvfb :3 -ac -screen sn 800x600x16 & $ ./parts/openoffice/program/soffice "-accept=socket,host=localhost,port=2002;urp;" -display :3 & $ ./bin/instance startThis recipe only works with linux at the moment
To test pyuno (requires zopepy in buildout.cfg):
$ ./bin/zopepy >>> import pyunoIf you get the fallowing error:
"SystemError: dynamic module not initialized properly"Do:
$ ldconfig YOURBUILDOUTFOLDER/parts/openoffice/programIf you still face the same error, you might try:
$ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:"YOURBUILDOUTFOLDER/parts/openoffice/program"Be careful that the first time you will run soffice in server mode, openoffice will oblige you to pass throught a wizard run first openoffice on your normal display or copy an .openoffice2 folder in the home of the user which is running the command.
This recipe requires rpm2cpio and cpio to be installed on your system.
Metadata
Release files for z3c.recipe.openoffice 0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| z3c.recipe.openoffice-0.3.tar.gz | 4.3 kB | Without provenance | Details for z3c.recipe.openoffice-0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| z3c.recipe.openoffice-0.3-py2.4.egg | Legacy Egg format | - | - | Details for z3c.recipe.openoffice-0.3-py2.4.egg |
Total release size: 13.7 kB
Release files / z3c.recipe.openoffice-0.3.tar.gz
| Download URL | z3c.recipe.openoffice-0.3.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5f74d56488a52bffe0d9a3fdfab1de5333b76fc773d0645c0db92276c3310ca3
|
|
BLAKE2b-256 checksum How to use checksums |
9c6bad39fa05a5243f80eeed7f5414853060a80b25fe8623b99d5aecf1e0b5fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / z3c.recipe.openoffice-0.3-py2.4.egg
| Download URL | z3c.recipe.openoffice-0.3-py2.4.egg |
|---|---|
| Size | 9.4 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
7c0ee38a0ad1a24357f00556f4bf60b7b0dca2d3d467f868a3ec330862079f6a
|
|
BLAKE2b-256 checksum How to use checksums |
22de786ba437c2acbda8d647dab0c7539d2e26b92fc5ff39b80203dbd5b6c3b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for z3c.recipe.openoffice 0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.