One script. Two editable Office documents.

If your workflow needs a Word report and a Korean Hangul document, the same Python code can create both:

from pywpdoc import Document

for fmt in ("docx", "hwpx"):
    doc = Document.new(fmt)
    doc.add_paragraph("Monthly report / 월간 보고서")
    doc.save(f"report.{fmt}")

Output: report.docx + report.hwpx—editable files, not PDF screenshots or renamed extensions. Desktop Word or Hancom is not required for ordinary creation and editing; native rendering/COM validation requires those applications.

Real native Windows PDF rendering of a historical synthetic test case. This is not a fresh 0.44.0rc1 visual-QA screenshot and does not imply identical Word/Hancom pagination. Image provenance · Current candidate QA evidence.

Why use PyWPDoc?

What makes it different? python-docx is a mature DOCX-specific library. PyWPDoc focuses on workflows that must handle both DOCX and HWPX; it does not replace every editor-specific feature.

Install

Until the first PyPI publication, use the public source checkout:

git clone https://github.com/rydolabs/PyWPDoc.git
cd PyWPDoc
python -m pip install -e ".[unified]"

After 0.44.0rc1 has actually been published to PyPI:

python -m pip install "pywpdoc[unified]==0.44.0rc1"

The [unified] extra installs python-docx for DOCX; pywpdoc alone suffices for HWPX-only work. Installation details.

Quickstart: a report with a table

from pywpdoc import Document

for fmt in ("docx", "hwpx"):
    doc = Document.new(fmt)
    doc.add_paragraph("Purchase request / 구매 요청서")
    table = doc.add_table(2, 2)
    table.cell(0, 0).text = "Item"
    table.cell(0, 1).text = "Quantity"
    table.cell(1, 0).text = "Notebook"
    table.cell(1, 1).text = "12"
    doc.save(f"purchase-request.{fmt}")

The runnable quickstart is exercised for both formats by API-contract CI tests.

Safer template filling

from pywpdoc import Document

doc = Document.open("template.hwpx")  # .docx works too
data = {"customer": {"name": "Example Ltd"}}
report = doc.check_template(data)       # read-only
if not report.ok:
    raise ValueError(f"Unresolved variables: {report.missing_keys}")
doc.render_template(data)
doc.save("filled.hwpx")

Template example · Preview and replace · Tracked comparison · Agent workflow example

Supported features and boundaries

save() does not convert file formats; rebuild() is not a universal lossless DOCX↔HWPX converter, and binary legacy .hwp input is not supported by Document.open(). Native expert APIs differ by backend. Compatibility · Known limitations.

Verified, with clearly stated limits

• Hosted CI: 10/10 jobs passed across Ubuntu/Windows Python 3.10–3.13, wheel/sdist and MkDocs checks. CI run.
• 0.44.0rc1 Windows native validation: 11/11 focused Word/Hancom cases, 7/7 extended QA stages, including long/stress documents. Evidence and exact scope.
• Historical visual outputs: a previous build passed 48/48 native PDF exports. The 0.44.0rc1 results archive has no new PDF/pixel-layout comparison.
• Public test suite: fixtures, omissions and skips are documented in tests/README.md. Hosted CI does not run desktop COM validation.

For AI coding assistants and agents

Use from pywpdoc import Document for portable operations. Pick the document format, preflight edits, and save in the same format. Treat doc.backend, doc.docx, doc.hwpx as expert-only APIs.

Task → API selection guide · Exact signatures · Machine-readable document index

PyWPDoc is a Python library—not a built-in MCP server or a native model tool. Publication does not guarantee ranking or selection by AI assistants.

한국어 · Documentation · Changelog · Security · Contributing · MIT License

Version: 0.44.0rc1 release candidate (GitHub Release and PyPI publication pending).