Repository navigation
feat(engine): bump itis-dakota 6.24.7->6.24.13, enable Python 3.14, retire 3.10/3.11 (T55kd) - #59
Merged
Merged
Conversation
…0, B22wk py3.14 fork-default, V50gm mp_context, V20qx/channel-policy amendments
…etire 3.10/3.11 (T55kd) - first 6.24.x with win_amd64 wheels -> Windows becomes a supported platform (CI gains tests-windows leg, py3.14); crosses the 6.24.8 cp311 drop: requires-python >=3.12,<3.15, .python-version 3.13, CI matrix 3.12/3.13/3.14 with the resolve warning-skip retired (broken lock now REDS) - verified on real wheels BEFORE pinning: full 454-test suite green on 3.12.10/3.13.7/3.14.8 incl. 26 analytical real-Dakota tests -> R5 no-op-fork-interface shim (B16mo) holds on 6.24.13, no upstream fix needed - B22wk: py3.14 flipped Linux multiprocessing default fork->forkserver; future_exec now pins an explicit mp_context (fork on POSIX, spawn on Windows) + requires_fork marker on the 3 mock-inheritance runner tests (V50gm) - floor-flip cleanups V41hp predicted: datetime.UTC x2, PEP695 overload type params, typing_extensions/tomli fallbacks removed (deps + scripts + call sites --with tomli dropped) - docs/README engine+py version sweep (had lagged two bumps at 1.5.9); dependabot ignore reason re-pointed at T55kd (V20qx guard updated) - uv.lock re-resolved (uv 0.13.1, lock revision 5)
…wner gate is the merge itself
CDLL(None)/PyDLL(None) + stdout/stderr symbol lookups are POSIX/macOS-only; the first windows-latest CI leg failed all 16 modules at collection. win32 now binds the shared UCRT (ucrtbase.dll: __acrt_iob_func(1/2) + fflush), POSIX path byte-identical; uv.lock synced to the bot's a12 bump
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
itis-dakota==6.24.7→6.24.13— first release withwin_amd64wheels (2026-10-06) → Windows becomes a supported platformrequires-python >=3.12,<3.15): the 6.24.8 cp311 drop is the cost, accepted by owner 2026-10-14; mmux/vite engine parity re-anchored to1.5.11(SPEC §C py)tests-windowsproof leg (py3.14)future_execnow pins an explicitmp_context(fork on POSIX / spawn on Windows) per new V50gm; 3 mock-inheritance runner tests getrequires_forkdatetime.UTC×2, PEP695 overload,typing_extensions/tomlifallbacks retired.python-version3.13,uv.lockre-resolvedVerified on real wheels before pinning
Full suite (unit + 26 analytical real-Dakota): 454 passed on 3.12.10, 3.13.7 and 3.14.8 with
itis-dakota==6.24.13; R5 no-op-fork-interface shim (B16mo) holds — no upstream fix needed.validatereportsVersion: 6.24.13.Ledger: T55kd, B22wk, V50gm, V20qx amendment (§SPEC.md).