No reason to print the value if it's 1, nor is there a reason to be so cryptic in the error message: just combine saying what it is with what is expected.

This is for a CI log, having a confirmation about LongPathsEnabled is useful (especially for LLMs to build context). Why do you not want to show that one line?

The output with the code as-is:

LongPathsEnabled = 0
::error::LongPathsEnabled is not set to 1 (see issue #1820)

Seems very clear to me:

• Problem: ::error::LongPathsEnabled is not set to 1
• Solution: see issue [BUG]: Windows CI runners need LongPathsEnabled for free-threaded Python #1820

The solution needs some explanation (unless you know about it already), so the pointer to the issue is a very efficient way to helpful.

I don't follow the LLM argument here. Is an LLM concerned about non failure case? Why does it need to have context in the boring, successful case. The context is there from the error message.

I personally despise output fluff like "build done" or "things went well", or just echoing information just because maybe it'll be useful someday.

Unless it's notable, actionable information, like a failure or actionable warning, then there should be no output. I'm not saying there are no exceptions to that, but this to me is a clear case of don't add any more spam to CI logs than necessary.