Sublime Forum

**michaelblyons** · January 10, 2020, 3:06pm

That looks like linting, which will be dependent on the linter you are using.

**volbil** · January 12, 2020, 9:46am

Thanks, after bit of ressearch on linters I figured my issue by installing MagicPython package for syntax highlight and flake8 package for linting

**mcoen78** · February 10, 2020, 10:54pm

Did you ever figure this out? I’m having the exact same problem (I’m using the same book you are) – I’m running 3.8.1 on macOS and get a syntax error.

**bschaaf** · February 11, 2020, 12:11am

You can verify whether the correct version of Python is being used by following OdatNurd’s reply.

**volbil** · February 12, 2020, 3:21am

Hello there, try this syntax package https://packagecontrol.io/packages/MagicPython
After that choose option to open Python files with MagicPython syntax.

For error highlighting and etc I’d recommend Anaconda package https://packagecontrol.io/packages/Anaconda

Maybe there is better solutions for f-string issue, but this is solution I came up with

**OdatNurd** · February 12, 2020, 3:44am

Just to reiterate what was stated above, the original problem(s) in the posts above have nothing to do with the syntax definition being deficient (as witnessed by the code in the screenshots being highlighted correctly); the actual problems seen by various posters are caused by:

A linter package that is linting Python 3 code as if it was Python 2
Trying to run Python 3 code using Python 2

In particular, Sublime executes an external program (the python interpreter) to run your code, so if running your program fails, that’s an issue with the external tool that’s being launched.

If you see some error indication in the gutter and/or colored boxes around code that’s invalid, that is a package you installed that’s trying to lint (verify) your code for you incorrectly assuming the version of Python that you’re using.

That’s not to say that the syntax provided by the MagicPython package isn’t somehow better for syntax highlighting purposes, but it’s by no means required to execute Python 3 code using f-strings.

**volbil** · February 12, 2020, 2:14pm

Problem is (as far as I understood) that Sublime is using build in version of Python 3.3.6 for syntax linting. I’ve tried dozen different ways to use macOS system version of Python but none of them worked, thats why I end up with such solution as MagicPython. Sure, it’s not solving original issue directly, but for me it was only way to overcome this limitation

**FichteFoll** · February 12, 2020, 5:12pm

No, it does not, because Sublime Text by itself does no syntax linting at all. It uses Python 3.3.6 for its plugin runtime, but it does not use that for linting. Linters using the SublimeLinter framework are external libraries or executables that are run on your code using whatever version you installed them for or configured.

**volbil** · February 13, 2020, 1:57am

Oh, I see, thanks for clarification. In this case there is issue with SublimeLinter framework on macOS. I’ve tried different ways outlined in this forum (including this thread and couple others), but none of them worked for me

**kakarukeys** · June 9, 2020, 3:11pm

I managed to solve this problem, it turned out I have unknowingly installed two plugins that use flake8 to lint my Python code, one of which was using a legacy python, the other I set to use the project’s python. Both of the linters were doing linting work and one of them was complaining about f-strings. That was what made it confusing. The solution was to turn the rogue linter off.

Does Python f-strings work?