Add the PyMEOS pin manifest and per-binding generator policy#96
Open
estebanzimanyi wants to merge 1 commit into
Open
Add the PyMEOS pin manifest and per-binding generator policy#96estebanzimanyi wants to merge 1 commit into
estebanzimanyi wants to merge 1 commit into
Conversation
master predates the meos-idl.json OO codegen, which lives in the open stack. Add tools/pin/compose-order.txt (the canonical fold manifest with the disposition of every open PR; MobilityDB#95 is the verified OO-codegen frontier containing MobilityDB#88/MobilityDB#89 and the family-switch stack) and GENERATION.md (the per-binding generator policy: PyMEOS is two layers — PyMEOS-CFFI low-level + the PyMEOS OO layer generated by tools/oo_codegen/codegen.py; the regular families switch to generated mixins generate-then-retire).
estebanzimanyi
force-pushed
the
tooling/canonical-generator-policy
branch
from
515118b to
63c61f0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Brings PyMEOS onto the ecosystem-wide per-binding generator policy (same treatment as JMEOS #29, GoMEOS #6, MEOS.NET #6, meos-rs #4):
tools/pin/compose-order.txt— PyMEOS's canonical, dependency-ordered fold manifest.masterpredates themeos-idl.jsonOO codegen, which lives in the open stack. This file fixes the composing set/order and records the disposition of every open PR.GENERATION.md— the per-binding generator policy. PyMEOS is two layers (like Rust'smeos-sys/meos): PyMEOS-CFFI (low-level, separate repo, its own manifest) + the PyMEOS OO layer generated bytools/oo_codegen/codegen.pyinto method-family mixins, with the RFC dispatch metadata as the path to 100% faithful codegen.Docs + manifest only — no code, no build impact.
Disposition of the open PRs (committer review)
Verified ancestry (
git merge-base, this turn): #95 is the OO-codegen frontier (14 commits overmaster) and contains #88 + #89 (and the family-switch stack #90–#93 + the #94 RFC).bump/meos-1.4feat/portable-aliasesfeat/oo-dispatch-consumerMisc PRs to triage separately (not the codegen story): #82 (1.3), #83 (min_distance), #84 (datalake), #85 (Black), #86 (cache pin); external #56/#72/#77.
Paired layer: PyMEOS-CFFI needs its own manifest +
GENERATION.md(its stack drivespymeos_cffi/functions.pyfrommeos-idl.jsonviabuilder/).Why
Per the per-binding generator policy: each binding owns its generator + its own pin manifest, the single source of truth is the MEOS-API catalog, and generation converges to a zero-hand-written surface via generate-then-retire.