python-office

pip install python-office 自动化办公专用库

Runs with mockssource: GitHubhomepagePythonApache-2.0commit dd6fe566f212

Python, Apache-2.0 licensed. The project labels itself: office, pip, pypi, python and weixin.

python-office runs, with stand-ins for the services it depends on. An Argusic agent installed it in 6 minutes and hit 12 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

python-office installs in .venv, imports as version 1.0.6; its pytest suite reaches 37 passing with 39 known-environment failures; PDF conversion (pdf2docx/split/merge/encrypt/decrypt), video2mp3, image compress/watermark, and QR-code workflows produce decodable output, and the PDF2Word GUI launches under Qt offscreen;

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.43 (measured)
recorded runs
1
last tested
stars
1,358
forks
303
open issues
34
watchers
14
size
20 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing python-office, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • missing test fixtures (tests/test_files) cause most file/excel/pdf/image test failures; the repo's own tests reference them but they are gitignored and not shipped4 minutes
  • PEP 668 externally-managed-environment blocked system pip install2 minutes
  • pytest test_optional_imports failed: office.api.web._load_pospider raised ImportError (AttributeError on absent pospider.url) instead of ModuleNotFoundError2 minutes
  • office.api.file had no search_by_content function while pofile's was a print-only stub and tests call it with content kwarg2 minutes
  • office.api.pdf.add_text_watermark called popdf.add_watermark (no-arg stub) causing TypeError2 minutes
  • GUI Qt xcb plugin fails (libxcb-xinerama.so.0 missing; system packages cannot be installed, no root)2 minutes
Install time
6 minutes
Cold machine to finish
26 minutes
Errors hit and fixed
12 hit, 12 fixed with no human help
How the result was proved
pytest tests/test_code -q: 37 passed, 39 failed, 2 skipped, 22 subtests passed; manual E2E: office.api.pdf pdf2docx/split4pdf/merge2pdf/encrypt4pdf/decrypt4pdf produced PDFs, ffmpeg -v error -i FILE -f null - decode exit 0 for /tmp/out.mp3, jpg outputs, qr png; office.api.video video2mp3 exit printed; GUI QT_QPA_PLATFORM=offscreen python gui/pdf2word/main.py stayed alive 6s and printed title PDF转Word工具
Model tokens used
2,337,479
Exact commit tested
dd6fe566f212
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

            stacklevel=2
        )
        if output_file is None:
            output_file = out_dir
    popdf.pdf2imgs(input_file=input_file, output_path=output_file, merge=merge)
Now I have complete findings. Time to compile the final result
exec
/bin/sh -lc "cd /work/repo && .venv/bin/python -c \"import office; print('import office ok:', offic…
 succeeded in 964ms:
import office ok: 1.0.6
tokens used
2,337,479

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 6 minutes.
  • Recovered from all 12 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.43

Topics (from GitHub)

officepippypipythonweixin

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/python-office.svg)](https://argusic.com/subject/python-office)

Questions

Does python-office run?
python-office runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 6 minutes, hitting 12 errors on the way, and recorded the session.
How did Argusic test python-office?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit dd6fe566f212. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test python-office?
The run that produced this verdict cost $0.43: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does python-office take to install?
6 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does python-office need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing python-office?
12 things broke in the recorded run, and 12 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for python-office?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion