Install Community, then prove one workbook operation locally

1. Start from a clean Python environment

Create an isolated environment, activate it, then install from public PyPI. The unpinned command deliberately resolves the maintained Community release rather than the separately distributed commercial line.

python -m venv .wolfxl-community
source .wolfxl-community/bin/activate
# Windows PowerShell: .\.wolfxl-community\Scripts\Activate.ps1
pip install wolfxl

View WolfXL Community on PyPI. Community is MIT-licensed and public; this command never needs a commercial credential.

2. Write and read a supported workbook

Run this in the activated environment. It creates report.xlsx, reopens it, and prints the value written to B2.

from wolfxl import Workbook, load_workbook

wb = Workbook()
ws = wb.active
ws["A1"] = "Region"
ws["B1"] = "Revenue"
ws["A2"] = "NA"
ws["B2"] = 125000
wb.save("report.xlsx")
wb.close()

check = load_workbook("report.xlsx")
print(check["Sheet"]["B2"].value)  # 125000
check.close()

Expected output: 125000.

3. Check the workflow boundary before migrating

This quickstart proves a supported new-workbook write and read. A production template workflow also needs evidence for its specific edits, formulas, package parts, and consumer application.

Need a commercial workflow assessment?

Native recalculation, render output, format conversion, VBA or Power Query operations, and the production operations SDK are commercial 2.1+ capabilities delivered through the authenticated package index. Start by checking the exact workbook workflow; the public Community package remains available independently on PyPI.