Skip to main content

Python Syntax & Comments


One of the biggest advantages of Python is it's syntax. It is easy to read, write and understand. 

In this article, I'm going to cover the below in brief.
  • Comments - How to write single line and multi line comments in Python
  • Variable definition - How to define variables in Python
  • End of statement - How does Python identify the end of a statement
  • Indentation - How integrated is indentation in Python syntax.


Comments are important part of any programming language. Python has two different ways of writing comments in the code. 
  • Multi-line comments 
  • Single-line comments 
Multi-line comments can be written by mentioning three quotes (''') at the beginning and ending of the comment.  


Multiple lines of comments
Usually written at the start of a program/function
describing usage of the program/function

Multi-line comments are helpful when we need to write few lines of comments to describe about a block of code, a function or a program. 

Single-line comments can be written with # and comment would end with End of line. 

# Single line comments end with End of Line
print("Hello...") # Print Hello

Variable Definition

Python is dynamically typed language and doesn't require variables to be defined with a specific data type. Python identifies the data type automatically based on the data passed into the variable. 


a = 10  # Integer
b = "B" # String

End Of Statement

Unlike most of other programming languages, Python doesn't use/require a semicolon (;) to indicate end of statement. End of line (CR LF) is usually considered and end of statement. 


a = 10
b = "B"

As soon as end of line is detected, Python assumes the end of statement and considers the next line as the next statement. 

We can also terminate a statement with semicolon (;). This usually helpful when we need to write multiple statements in a single line. 

a = 10; b = "B"

What if the statement is too big and has to extend beyond a line? Using '\' at the end of the line would help if a statement is going beyond single line. 

c = "This is a big statement " \
"and has to extend beyond single line."

d = a/2 +\

Above two statements are equal to the below. 

c = "This is a big statement and has to extend beyond single line."

d = a/2 + 100

This can also be done by enclosing with in parenthesis. 

c = ("This is a big statement " +
"and has to extend beyond single line.")

d = (a / 2 +


Indentation is recommended in any programming language to make the code easy to understand. In Python, indentation is mandatory to indicate/write a block of code. 

There is no restriction on how many spaces are to be used, but number of spaces need to be consistent in a block of code. But, 4 spaces are widely used.

# This function uses 4 blank spaces
def printA():
a = 10

# This function uses 2 blank spaces
def printB():
b = "B"

But, we cannot have different spaces in the same block of code. 

# This function uses 4 blank spaces
def printA():
a = 10

Having different number of spaces would cause the program to throw IndentationError (IndentationError: unindent does not match any outer indentation level) 

A block of code doesn't necessarily be a function, it can also be a condition or loop. 

# This function uses 4 blank spaces
def printA():
a = 10
b = 20

# This condition uses 2 blank spaces
if (a > b):
print("a is greater than b")
# Code with in else block uses 8 blank spaces
print("b is greater than a")

In the above code, 
  • Statements with in printA function including if and else, are to follow the same indentation. 
  • Any code under if or else need to use the same indentation. 
One thing to note here is, A block of code would always be preceded by colon (:).

Hope the above content has been of some help to you. 

If you have any Suggestions or Feedback, Please leave a comment below or use Contact Form.


Popular posts from this blog

All about READ in RPGLE & Why we use it with SETLL/SETGT?

READ READ is one of the most used Opcodes in RPGLE. As the name suggests main purpose of this Opcode is to read a record from Database file. What are the different READ Opcodes? To list, Below are the five Opcodes.  READ - Read a Record READC - Read Next Changed Record READE - Read Equal Key Record READP - Read Prior Record READPE - Read Prior Equal Record We will see more about each of these later in this article. Before that, We will see a bit about SETLL/SETGT .  SETLL (Set Lower Limit) SETLL accepts Key Fields or Relative Record Number (RRN) as Search Arguments and positions the file at the Corresponding Record (or Next Record if exact match isn't found).  SETGT (Set Greater Than) SETGT accepts Key Fields or Relative Record Number (RRN) as Search Arguments and positions the file at the Next Record (Greater Than the Key value). Syntax: SETLL SEARCH-ARGUMENTS/KEYFIELDS FILENAME SETGT  SEARCH-ARGUMENTS/KEYFIELDS FILENAME One of the below can be passed as Search Arguments. Key Fiel

What we need to know about CHAIN (RPGLE) & How is it different from READ?

CHAIN READ & CHAIN, These are one of the most used (& useful) Opcodes by any RPG developer. These Opcodes are used to read a record from file. So, What's the difference between CHAIN & READ?   CHAIN operation retrieves a record based on the Key specified. It's more like Retrieving Random record from a Database file based on the Key fields.  READ operation reads the record currently pointed to from a Database file. There are multiple Opcodes that start with READ and all are used to read a record but with slight difference. We will see more about different Opcodes and How they are different from each other (and CHAIN) in another article. Few differences to note.  CHAIN requires Key fields to read a record where as READ would read the record currently pointed to (SETLL or SETGT are used to point a Record).  If there are multiple records with the same Key data, CHAIN would return the same record every time. READE can be used to read all the records with the specified Ke

Extract a portion of a Date/Time/Timestamp in RPGLE - IBM i

%SUBDT Extracting Year, Month, Day, Hour, Minutes, Seconds or Milli seconds of a given Date/Time/Timestamp is required most of the times.  This can be extracted easily by using %SUBDT. BIF name looks more similar to %SUBST which is used to extract a portion of string by passing from and two positions of the original string. Instead, We would need to pass a value (i.e., Date, Time or Timestamp ) and Unit (i.e., *YEARS, *MONTHS, *DAYS, *HOURS, *MINUTES, *SECONDS or *MSECONDS) to %SUBDT.  Valid unit should be passed for the type of the value passed. Below are the valid values for each type. Date - *DAYS, *MONTHS, *YEARS Time - *HOURS, *MINUTES, *SECONDS Timestamp - *DAYS, *MONTHS, *YEARS, *HOURS, *MINUTES, *SECONDS, *MSECONDS Syntax: %SUBDT(value : unit { : digits { : decpos} }) Value and Unit are the mandatory arguments.  Digits and Decimal positions are optional and can only be used with *SECONDS for Timestamp. We can either pass the full form for the unit or use the short form. Below i