1.4.2

1.4.2

A defect-fix release. Nothing about how you write a code block changed; every entry below is something that was wrong on screen.

Fixed

• A snippet that prints nothing can be run again without clearing the output first. 1.4.0's completion notice is written into the output area before the program runs, and the plugin treated "the output area has something in it" and "the program printed something" as the same question — so a fragment that only computes (int x = 41 + 1;) left ▶ replaced by ✕, and running it again meant clearing the output first. The two questions are asked separately now. Nothing else about the buttons changed: as soon as the program prints anything of its own — including a compiler warning — ✕ is back, exactly as before 1.4.0.
• A Chinese interface no longer shows an English sentence when a program prints nothing. The compile service used by C, C++, Java, Go, C#, Swift and R answers a silent, correct run with its own English placeholder, No output. — the same literal for all seven languages, and in English no matter what language you use the plugin in. The plugin now writes its own sentence in its place, in your language. That sentence is treated as the plugin's, not the program's, so it cannot bring the button problem above back with it.
• No more 3 个错误s. Three translation defects, all in the Chinese text:
  • The error and warning counts carried English's plural suffix into Chinese, where it does not belong.
  • The two counts were joined with an English comma — 1 个错误, 1 个警告 — which reads as a typo in Chinese. It is a full-width comma now.
  • One message from the Python Worker (Unknown error, the fallback when an error arrives without a description) was a bare English string in a file that translates everything else.
• A Python error no longer shows the runtime's own stack. print(undefined_name) printed five lines, two of them File "/lib/python312.zip/_pyodide/_base.py" — frames inside the Python runtime rather than in your code. They are gone; the traceback now opens with your own File "<exec>" line. If the error happens inside a function you wrote, every one of your frames is still shown.

Full changelog: 1.4.1...1.4.2