ps-python-docx
ps-python-docx is John Paul Ellis's fork of python-docx, a Python library for reading, creating, and updating Microsoft Word 2007+ (.docx) files. It is published independently and is not an official upstream release.
This fork starts from upstream 1.2.0. The packaging setup preserves the upstream API and the docx import name. Version 1.3.0 adds public theme font and style inheritance APIs. See the theme API documentation. The original MIT license and upstream attribution are preserved.
Version 1.3.1 adds public external hyperlink authoring with Paragraph.add_hyperlink(), formatted label runs with Hyperlink.add_run(), and read/write tooltip support. See the text API documentation.
Version 1.3.2 adds InlineShape.description and InlineShape.title for reading and writing image alternative text. See the image metadata documentation.
Version 1.3.3 adds independent list instances, starts and restarts, template levels, and unnumbered continuation paragraphs. See the list documentation.
Version 1.3.4 adds bookmark creation and lookup with Document.bookmarks, plus internal hyperlinks with Paragraph.add_hyperlink(anchor=...). See the bookmark documentation.
Installation
pip install ps-python-docx
Example
>>> from docx import Document
>>> document = Document()
>>> document.add_paragraph("It was a dark and stormy night.")
<docx.text.paragraph.Paragraph object at 0x10f19e760>
>>> document.save("dark-and-stormy.docx")
>>> document = Document("dark-and-stormy.docx")
>>> document.paragraphs[0].text
'It was a dark and stormy night.'
Install this distribution in place of python-docx. Both provide the docx package and should not be installed in the same environment.
More information about the inherited API is available in the upstream documentation. Report fork-specific issues in this repository.
Development and releases
Run the unit and acceptance suites without installing the legacy documentation dependencies:
uv sync --locked --no-dev --group test
uv run --locked --no-dev --group test pytest -q
uv run --locked --no-dev --group test behave --format progress --stop --tags=-wip
See RELEASING.md for the GitHub-to-PyPI release process.
Release files for ps-python-docx 1.3.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ps_python_docx-1.3.4.tar.gz | 5.7 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ps_python_docx-1.3.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.0 MB
Release files / ps_python_docx-1.3.4.tar.gz
| Download URL | ps_python_docx-1.3.4.tar.gz |
|---|---|
| Size | 5.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
79041d62696d76a5d7bd283a255ae8ae98bd1cb6d2ae83048e98c337dc58c6d4
|
|
BLAKE2b-256 checksum How to use checksums |
8d756275a0b2dfcd6470e53a136d2dccfe5b0b02a746e0021b2ea6b5db6dfd6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Sep 24, 2026.
Transparency logRelease files / ps_python_docx-1.3.4-py3-none-any.whl
| Download URL | ps_python_docx-1.3.4-py3-none-any.whl |
|---|---|
| Size | 265.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fbbc5fecc699a10996cb6ee1119873b675d0ca85bbab2445e0bd1b342ea933b5
|
|
BLAKE2b-256 checksum How to use checksums |
16a5874889baf97c3caf89ef11ce371560f7dd8c3d7322b8dc8d5f6a8ee529c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Sep 24, 2026.
Transparency log