ci: pin Nuitka to 4.1.3 - #601
Open
FelipeDefensor wants to merge 1 commit into
Open
Conversation
The v0.6.5 build compiled cleanly on every platform and then failed the
smoke test on Linux and both macOS runners: the executable dies at
startup with
File ".../music21/bar.py", line 211, in <module music21.bar>
AttributeError: module 'music21.repeat' has no attribute 'RepeatMark'
music21.bar reads repeat.RepeatMark at module level while music21.repeat
is still initialising. CPython's import ordering resolves that; Nuitka
4.2.1's does not.
The dependency group had no upper bound, so CI moved from 4.1.3 to 4.2.1
on its own. Nothing else changed: v0.6.4 built green on 2026-07-28 with
the same music21 10.5.0 and the same PySide6 6.9.3, and the import chain
that crashes (qtui -> parsers.csv.harmony -> music21) is untouched
between the two tags -- v0.6.5 changes five files in tilia/, none of them
under tilia/parsers/.
Pin the version that is known to produce a working executable. Left
[build-system] requires alone: that Nuitka only ever exists in the
isolated PEP 517 environment for `pip install -e .`, while deploy.py
compiles with the one from this group.
Collaborator
|
This is fixed in the velopack branch |
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
2 participants
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.
Carries the pin from the v0.6.5 release branch over to
dev, so the next release build does not walk into the same wall.What happened
The first
v0.6.5build compiled cleanly on every platform and then failed the smoke test on Linux and both macOS runners — the executable dies at startup:music21.barreadsrepeat.RepeatMarkat module level whilemusic21.repeatis still initialising. CPython's import ordering resolves that; Nuitka 4.2.1's does not.Why it is Nuitka and not us
The
builddependency group had no upper bound, so CI moved from 4.1.3 to 4.2.1 on its own. Comparing the last green build with the failing one:And the crashing import chain (
qtui→parsers.csv.harmony→music21) is untouched between the two tags: v0.6.5 changes five files undertilia/, none of them intilia/parsers/.Scope
[build-system] requiresis deliberately left alone — that Nuitka only ever exists in the isolated PEP 517 environment forpip install -e ., whilescripts/deploy.pycompiles with the one from thebuildgroup.The rebuild on the release branch, with 4.1.3 pinned, is what confirms this;
at the time of writing it is still running. If it comes back red this PR
should wait, since the pin would then not be the whole story.