DECISION: release the one-solid Part and the fixes on dev as 2.2.9. The version number is 2.2.9, not 2.2.8 again and not 2.2.8.post1. WHY - THE DISCUSSION (owner and assistant, 2026-11-10) - 2.2.8 shipped a Part that could hold several bodies. The audit found such a Part could not take part in an assembly (no connectors, explode_rassembly raised); the owner judged the multi-body Part a wrong decision made for the editor's convenience, and the agreed answer was Part = one solid, the editor shows loose solids (design-docs/part-holds-one-solid.md, merged in the pull request "A Part holds exactly one solid"). - The owner deleted the GitHub release of 2.2.8 and yanked 2.2.8 on PyPI. The owner asked whether 2.2.8 could be published again: it cannot. PyPI keeps a version and its file names for ever, even when yanked or deleted, and does not accept another upload under them. So the fixed code needs a new number. - 2.2.9 rather than 2.2.8.post1: the change removes interface that 2.2.8 had (`bodies=`, `inspect_body_overlaps_rlist`, `part_shape`, profile 3), which a patch number says more plainly than a post-release of a withdrawn version; this repository's `.post1` / `.post2` releases (2.2.6) were for packaging fixes. WHAT CHANGES (the same files as "release: 2.2.8" touched) - pyproject.toml, uv.lock (the simplecadapi package entry), docs/skill/SKILL.md (version, package-version) and docs/skill/references/SDK_OVERVIEW.md: 2.2.8 -> 2.2.9. - CHANGELOG.md: the Unreleased entry of the one-solid change becomes 2.2.9 (2026-11-10), with a Fixed section for what else is on dev since the 2.2.8 tag: the Windows editor pid probe, GCC 14 and MinGW source builds, macOS wheels on macos-15. - docs/updates/2.2.9.md and 2.2.9.zh-CN.md: the update notes, which the release workflow turns into the release page. They say that 2.2.8 is withdrawn, why a Part holds one solid, what changes for users (the argument and helpers removed, SeveralOpenBodiesError, the editor's open solids) and what was fixed. Checked: nothing in the tests reads these files; the release workflow checks that the tag equals the pyproject version (v2.2.9). The wheels and the PyPI upload are built by the workflow when the tag is pushed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
3.4 KiB
2.2.9 Update Notes
2.2.9 replaces 2.2.8, which has been withdrawn (yanked on PyPI, its GitHub release deleted). 2.2.8 let a Part hold several
bodies, and a Part like that could not take part in an assembly. In 2.2.9 a Part holds exactly one solid again, and the
editor keeps what it needed from the change: several solids can sit side by side in a notebook while a model is built.
Everything else in 2.2.8 is in 2.2.9; the 2.2.8 notes describe it.
Why a Part holds one solid
The editor has to let several solids exist in one notebook with no assembly constraint between them: to pattern a tool and then cut, there is a moment where more than one tool and the body exist together. In 2.2.8 that was solved inside the Part. But a Part is the unit an assembly places, mates and gives connectors to, and a Part of several bodies could do none of that:
- connectors on it were refused, so no mate or public connector could reach it;
explode_rassemblyraisedTypeErroron any assembly that held one;- the older scene compiler read the single body of a Part in four places.
The solids side by side are intermediate values of a notebook, not product items. So they are notebook values now, and the
Part is one solid. The full account is in design-docs/part-holds-one-solid.md; every commit of the change states its own
reason.
What changes for you
make_part_rpart(part_id, body, name=None)takes one Solid, aBody(a solid with a display name, colour and opacity), or a list of exactly one piece of a split cut. Several solids raiseValueError, which says what to do: one Part per solid in an Assembly (identity placements when they only sit together), or union / cut them into one solid first.- Removed (they only existed in the withdrawn 2.2.8): the
bodies=argument,Part.multi_body,scad.part_shape,inspect_body_overlaps_rlist,BodyOverlap,BodyOverlapWarning, and the part definition profilesimplecad-part-definition-3withsolid_cache.bodies. A part definition is profile 2 with one solid, as before 2.2.8. A model JSON recorded with several solids in one Part is refused on replay, with the same guidance. - A part notebook with one open solid (
kind = "part", no cell making the Part) still gets the implicit Part. With several open solids there is no product: running it raisesSeveralOpenBodiesError, which names the solids; make the Part from the one that is the part (scad.make_part_rpart(part_id=scad.notebook_id(), body=...)), or make a Part of each and an Assembly of them. - The editor draws such open solids side by side and its header says "N open solids";
use_as_productmakes the Part from the solid you choose. One-body Parts,Pieces(the result of a splitting cut), connectors, mates andexplode_rassemblybehave as they did.
Fixed
- On Windows,
sca cellno longer kills the editor it talks to: the editor's process id is probed without signalling it (os.kill(pid, 0)on Windows terminates the process). - Building from source: GCC 14 (
operators_promote.cppincludes<algorithm>), MinGW (_USE_MATH_DEFINES, andbuild_occt.pypicks Ninja when a MinGWg++is the compiler), and the macOS wheels are built onmacos-15(GitHub no longer servesmacos-14; the wheels still target macOS 14.0).
For contributors
AGENT.mdrecords how to rebuild the C++ module on Windows and how commits are organised: one decision per commit, with the reasons from the discussion that led to it.