Add the PyMEOS-CFFI pin manifest and per-binding generator policy#21
Open
estebanzimanyi wants to merge 1 commit into
Open
Add the PyMEOS-CFFI pin manifest and per-binding generator policy#21estebanzimanyi wants to merge 1 commit into
estebanzimanyi wants to merge 1 commit into
Conversation
master predates the meos-idl.json-driven codegen, which lives in the open stack. Add tools/pin/compose-order.txt (the canonical fold manifest; MobilityDB#19 is the verified frontier containing MobilityDB#18) and GENERATION.md (the per-binding generator policy: PyMEOS-CFFI owns its generator in-repo at builder/build_pymeos_functions.py generating pymeos_cffi/functions.py from meos-idl.json; the low-level CFFI layer under the PyMEOS OO layer).
estebanzimanyi
force-pushed
the
tooling/canonical-generator-policy
branch
from
b3eb97f to
c29d724
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-CFFI (the low-level CFFI layer under PyMEOS) onto the ecosystem-wide per-binding generator policy (same treatment as JMEOS #29, GoMEOS #6, MEOS.NET #6, meos-rs #4, PyMEOS #96):
tools/pin/compose-order.txt— the canonical, dependency-ordered fold manifest.masterpredates themeos-idl.json-driven codegen, which lives in the open stack.GENERATION.md— the per-binding generator policy: PyMEOS-CFFI owns its generator in-repo atbuilder/(build_pymeos_functions.pyreadsbuilder/meos-idl.json→pymeos_cffi/functions.py); the low-level CFFI layer (analog of Rust'smeos-sys) under the PyMEOS OO layer.Docs + manifest only — no code, no build impact.
Disposition of the open PRs (committer review)
Verified ancestry (
git merge-base, this turn): #19 is the frontier (17 commits overmaster) and contains #18.bump/meos-1.4refactor/codegen-meos-idlfunctions.pycodegen frommeos-idl.jsonbump/meos-1.3add-from-arrays2Why
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.