Google Python tutorial uses syntax inconsistent with my IDE (VS Code)

[nightmarevoid]

I'm trying to brush up on python using Google's python tutorials and by doing the exercises in VS Code, but the syntax is inconsistent between google's code and what the IDE expects. I'm using python 3.9.6 as the interpreter.

 

take for instance print. Should be straight forward, but google doesn't use a lot of syntax that VS Code is expecting. for example

#google exercises are written as

print 'hello world'

#VS Code throws errors
#It says things like "declarations should be on a new line)
#the tool tip for print shows everything in parenthesis
#It expects

print('hello world')

This is pretty frustrating because I have to spend time debugging google's own code. The worst part is that I'm not a big fan of google and wish they would do things differently, so spending time debugging their code while trying to use their resources is a level of cosmic irony I wasn't prepared for today.

 

to use python on VS code I'm using two extensions: "Python" by Microsoft and "Python Extension Pack" by Don Jayamanne

 

Is this discrepancy down to the python 3.9 interpreter being different, VS Code adding syntax where it isn't supposed to be, or google writing in an outdated form of Python? How can I fix it?

 

 

[igormp]

Google's available code online is usually old.

 

The code you quoted is Python 2, so you need to use a python 2.7 interpreter instead of the 3.9.6 you're currently using.

[Biohazard777]

34 minutes ago, nightmarevoid said:

I'm trying to brush up on python using Google's python tutorials and by doing the exercises in VS Code, but the syntax is inconsistent between google's code and what the IDE expects. I'm using python 3.9.6 as the interpreter.

 

take for instance print. Should be straight forward, but google doesn't use a lot of syntax that VS Code is expecting. for example

#google exercises are written as

print 'hello world'

#VS Code throws errors
#It says things like "declarations should be on a new line)
#the tool tip for print shows everything in parenthesis
#It expects

print('hello world')

This is pretty frustrating because I have to spend time debugging google's own code. The worst part is that I'm not a big fan of google and wish they would do things differently, so spending time debugging their code while trying to use their resources is a level of cosmic irony I wasn't prepared for today.

 

to use python on VS code I'm using two extensions: "Python" by Microsoft and "Python Extension Pack" by Don Jayamanne

 

Is this discrepancy down to the python 3.9 interpreter being different, VS Code adding syntax where it isn't supposed to be, or google writing in an outdated form of Python? How can I fix it?

 

 

You are probably following a python 2 tutorial, no parenthesis:

https://docs.python.org/2/tutorial/inputoutput.html

While in python 3 you should use parenthesis:

https://docs.python.org/3/tutorial/inputoutput.html

 

Always check the official documentation when in doubt 

 

[Sauron]

7 hours ago, nightmarevoid said:

print 'hello world'

this is the python 2 version, python 3 syntax is different.

[Chubak]

Just so you know, your IDE has nothing to do with the syntax. The IDE uses pylint to lint your code, then VSCode looks for which version of Python you're using (bottom-left corner) to give pylint that version to lint. In other words, you can use Notepad to write code and use pylint to lint, it's still the same operation.

All IDEs do is to provide tools for programming languages, they aren't involved in the compilers/interpreters themselves.

[pythonmegapixel]

6 hours ago, Chubak said:

Just so you know, your IDE has nothing to do with the syntax. The IDE uses pylint to lint your code, then VSCode looks for which version of Python you're using (bottom-left corner) to give pylint that version to lint. In other words, you can use Notepad to write code and use pylint to lint, it's still the same operation.

All IDEs do is to provide tools for programming languages, they aren't involved in the compilers/interpreters themselves.

Mostly correct. The IDE having nothing to do with syntax isn't really true though, because the vast vast majority of them perform syntax highlighting and some have more advanced syntax-based features than that (e.g. identifying unused libraries that you've imported). So the IDE does need to know what syntax to expect to perform those functions in an effective manner.