pyJianYingDraft
轻量、灵活、易上手的Python剪映草稿生成及导出工具，构建全自动化视频剪辑/混剪流水线。本项目的CapCut版本正于 https://github.com/GuanYixuan/pyCapCut 内开发
Runs with mockssource: GitHubPythonApache-2.0commit c3318066d964
Python, Apache-2.0 licensed. The project labels itself: api, automation, capcut, jianying, video editing and video production.
pyJianYingDraft runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.3 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
pyJianYingDraft 0.3.0 installed in a venv, all 44 tests pass, and the core API (ScriptFile, TextSegment, DraftFolder, template loading, time utilities) runs correctly on Linux.
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 86 of 100 (the mean of this project's run scores).
At a glance
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- test_duplicate_as_template_reuses_fallback_loader failed on Linux due to hardcoded Windows path separator (backslash)0.1 minutes
- Install time
- under a minute
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- pytest tests/ --tb=no -q: 44 passed in 0.17s. Also verified core API: ScriptFile creation, trange/time utilities, TextSegment creation, JSON dump/export, DraftFolder create/save/load cycle.
- Model tokens used
- 52,418
- Exact commit tested
- c3318066d964
- 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.
pyJianYingDraft/video_segment.py:649:141: E501 line too long (147 > 140 characters) tests/test_template_loading.py:72:141: E501 line too long (142 > 140 characters) tests/test_track_insert_api.py:52:5: F841 local variable 'second_ref' is assigned to but never used These are pre-existing linter warnings (some are type-checker hints using `F821` for forward refere… Let me now compile the final summary exec /bin/sh -lc 'cd /work/repo && /tmp/venv/bin/python -m pytest tests/ --tb=no -q 2>&1' in /work/repo succeeded in 268ms: ............................................ [100%] 44 passed in 0.17s tokens used 52,418
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 0.3 minutes.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
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.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.02 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.02 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/pyjianyingdraft)Questions
- Does pyJianYingDraft run?
- pyJianYingDraft runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test pyJianYingDraft?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c3318066d964. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test pyJianYingDraft?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does pyJianYingDraft take to install?
- 0.3 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 pyJianYingDraft need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing pyJianYingDraft?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for pyJianYingDraft?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.