No problems are found in the code snippet below.
Pylance finds problems because it incorrectly interprets the Unicode character \N{combining enclosing keycap} as an expression inside the f-string.
N/A
num_emojis = [f"{i}\N{combining enclosing keycap}" for i in range(1, 10)] + ["\N{keycap ten}"]


Thanks for the bug report. This isn't related to f-strings specifically. It affects other string literals too. Pyright/pylance is not properly handling escaped unicode names that contain spaces. I've fixed the problem, and it will be addressed in the next version of pyright/pylance.
This issue has been fixed in version 2020.7.0, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/master/CHANGELOG.md#202070-9-july-2020