From the C99 standard:

In translation phase 6, the multibyte character sequences specified by any sequence of adjacent character and identically-prefixed string literal tokens are concatenated into a single multibyte character sequence. If any of the tokens has an encoding prefix, the resulting multibyte character sequence is treated as having the same prefix; otherwise, it is treated as a character string literal. Whether differently-prefixed wide string literal tokens can be concatenated and, if so, the treatment of the resulting multibyte character sequence are implementation-defined.

@serhiy-storchaka Does it occur to you if there is a simpler way to produce this string at compile time?

🤖 New build scheduled with the buildbot fleet by @pablogsal for commit 4211927 🤖

If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again.

Seems that the almost all buildbot workers are green and the ones that fail are because some other unrelated issues (no space left on device and some PGO/LTO failures elsewhere). So I am going ahead and merge this

CC: @ambv

Thanks @pablogsal for the PR 🌮🎉.. I'm working now to backport this PR to: 3.9.
🐍🍒⛏🤖

Sorry, @pablogsal, I could not cleanly backport this to 3.9 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker 2a561b5f6830aee39cf05dc70c24e26c3558dda0 3.9

@pablogsal: I don't think that we need a backport to 3.9 which only uses a single digit for the minor version.

@pablogsal: I don't think that we need a backport to 3.9 which only uses a single digit for the minor version.

Makes sense, I just wanted to extend the progress 😅