pyodr — Python bindings for OpenDocument.core
Decode office documents (ODF, OOXML, legacy MS binary, PDF, CSV, ...) and render them to HTML from Python.
import pyodr
file = pyodr.open("document.odt")
print(pyodr.file_type_to_string(file.file_type()))
service = pyodr.html.translate(file, "cache-dir", pyodr.HtmlConfig())
html = service.bring_offline("output-dir")
for page in html.pages():
print(page.name, page.path)
A small CLI is included: pyodr <file> renders a document and opens it in the
browser; pyodr <file> --serve hosts it over HTTP (via the core HTTP server,
available when built with ODR_WITH_HTTP_SERVER).
Building
The bindings are part of the main CMake build, toggled by ODR_PYTHON:
conan install . -o '&:with_python=True' --build missing
cmake -B build -S . -DCMAKE_TOOLCHAIN_FILE=conan_toolchain.cmake -DODR_PYTHON=ON
cmake --build build --target pyodr_core
PYTHONPATH=build/python python -m pytest python/tests
pip install . from the repository root builds a wheel via scikit-build-core
(see the root pyproject.toml); run conan install first and point
CMAKE_ARGS at the generated conan_toolchain.cmake so the C++ dependencies
resolve:
conan install . -o '&:with_python=True' --build missing
CMAKE_ARGS="-DCMAKE_TOOLCHAIN_FILE=$PWD/conan_toolchain.cmake" pip install .
Runtime data
There is none. The renderer's css and js are part of the library, so rendering
works out of the box; odr_core_data_path() and set_odr_core_data_path(...)
are deprecated leftovers that still store and return a path nothing reads.
MIME detection needs no runtime data: mimetype runs the open strategy, so it
names what is inside a zip or a compound file. libmagic_database_path() and
set_libmagic_database_path(...) are deprecated leftovers of the libmagic
backend that used to answer this and could only say application/zip for an
.odt; they still store and return a path, but nothing reads it.
1 maintainer
Metadata
1 maintainer
Release files for pyodr 6.10.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pyodr-6.10.0.tar.gz | 1.5 MB | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyodr-6.10.0-cp314-cp314-manylinux_2_39_x86_64.whl | CPython 3.14 | CPython 3.14 | Linux glibc 2.39+ x86-64 | Details |
| pyodr-6.10.0-cp314-cp314-macosx_26_0_arm64.whl | CPython 3.14 | CPython 3.14 | macOS 26.0+ ARM64 | Details |
Total release size: 7.1 MB
Release files / pyodr-6.10.0.tar.gz
| Download URL | pyodr-6.10.0.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
13a2d8179fa962d0e604e4bb0a45eb50fae4c3fe6783ab8fca3ea88b65462007
|
|
BLAKE2b-256 checksum How to use checksums |
cb862c4f2ad328a3f23ca0dbfab8e67cb771351d0e460c8e3c6b8e99b868de4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 21, 2026.
Transparency logRelease files / pyodr-6.10.0-cp314-cp314-manylinux_2_39_x86_64.whl
| Download URL | pyodr-6.10.0-cp314-cp314-manylinux_2_39_x86_64.whl |
|---|---|
| Size | 3.3 MB |
| Tags | CPython 3.14 Linux glibc 2.39+ x86-64 |
|
SHA-256 checksum How to use checksums |
cc74dd0667ad7f88ff0aa7b34776ed380c82463fe6ea7714752155bb1b098e6a
|
|
BLAKE2b-256 checksum How to use checksums |
e78f987c62bc34f5607f3913e4953552aaccb438ff045ee724caf4b4c81e5f3a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 21, 2026.
Transparency logRelease files / pyodr-6.10.0-cp314-cp314-macosx_26_0_arm64.whl
| Download URL | pyodr-6.10.0-cp314-cp314-macosx_26_0_arm64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.14 macOS 26.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
4a18c1c86b8bc37ab1f4819a1e4ec150e2362592bd0d25afa950976a444f71c9
|
|
BLAKE2b-256 checksum How to use checksums |
f0be1cab6caf12a76ad294cbf5dd243c325e0d8ef3a970e1caa42c55d6a51ced
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 21, 2026.
Transparency log
