Skip to content

Fail closed when manim.unsafe_unicode is not a YAML list - #96

Merged
cursor[bot] merged 2 commits into
mainfrom
cursor/manim-unsafe-unicode-2ccd
Sep 7, 2026
Merged

cursor[bot] merged 2 commits into
mainfrom
cursor/manim-unsafe-unicode-2ccd

Conversation

@jmjava

@jmjava jmjava commented Sep 7, 2026

Copy link
Copy Markdown
Owner

Problem

manim.unsafe_unicode as a YAML string already raised ConfigError when the property was read (validate / scene-spec-generate). Config.from_yaml did not touch it, so yaml-generate, tts, and other commands could load a bad file.

Change

Evaluate manim_unsafe_unicode during Config.from_yaml (same as manim.scenes). Use string_list_block so items must be YAML strings. Missing/null still uses the built-in Pango fallback list; [] still disables unicode lint.

Milestone: milestones/manim-unsafe-unicode.md

Out of scope

  • The default character list itself is unchanged.
Open in Web Open in Cursor 

cursoragent and others added 2 commits September 7, 2026 20:01
The property already raised on a scalar, but only when validate or
scene-spec-generate read it. Evaluate it in Config.from_yaml and require
string list items, matching manim.scenes.

Co-authored-by: jmjava <jmjava@gmail.com>
Local ruff, pytest, and docgen benchmark are green on this branch.

Co-authored-by: jmjava <jmjava@gmail.com>
@jmjava
jmjava marked this pull request as ready for review September 7, 2026 20:02
@cursor
cursor Bot merged commit 5e191d8 into main Sep 7, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants