Skip to main content

How to Iterate Over a List and Get Indexes with 'enumerate' Function in Python

'enumerate' function

There are different ways of accessing the data from a list like using range and then index or accessing the element of a list directly from for loop and so on. 

One other powerful way is by using 'enumerate' function. One major advantage of using 'enumerate' is this function returns both index and corresponding element at once. So, we don't have to maintain a counter to calculate the index or need to retrieve the element from a index. This makes the code easy to maintain and understand. 

In this post, we will see how to use 'enumerate' function and looping over a list to access index and elements as a tuple and also by using tuple unpacking

Syntax

enumerate(iterable, start=0)

'enumerate' function accepts two parameters. 
  • 'iterable' - This is a mandatory parameter. An iterable (E.g.: list, tuple, string...) on which we need to run the loop and retrieve index and element.
  • 'start' - This is an optional parameter. 'start' specifies the number of the first index (This works more like a counter than index). Default value is '0'. 
Let's have a look at an example for looping over a list using enumerate. 

1

2

3

4

5

fruits = ['apple', 'banana', 'cherry']


for index, fruit in enumerate(fruits):

   print(index, fruit)



In the above example, we are only passing the list to the enumerate function, so start index would be considered as '0' and returns the index and element combination for every iteration. Below is the result. 

0 apple

1 banana

2 cherry


Let's have another example by passing an optional parameter 'start'. 

1

2

3

4

5

fruits = ['apple', 'banana', 'cherry']


for index, fruit in enumerate(fruits, 1):

   print(index, fruit)



In the above example, we are passing '1' as the start. One thing to here is, it is not like slicing where the loop is iterated from the index passed for 'start'. Instead, enumerate start indexing from '1'. It is better understood by looking at the result. 

1 apple

2 banana

3 cherry


This can be useful in the cases where we need to start numbering from '1' (or any other number instead of zero) and continue till the end of the list. 

In the above examples, we are directly unpacking the tuple from 'enumerate' function as index and fruit. 

We can also use it as a tuple instead. 

1

2

3

4

5

fruits = ['apple', 'banana', 'cherry']


for fruit_tuple in enumerate(fruits, 1):

   print(fruit_tuple)



Unlike previous examples, we are not using two different variables (for index and element) in for loop, instead we are only passing one variable. In this case, index and element combination is returned as a tuple. Below is the result.

(1, 'apple')

(2, 'banana')

(3, 'cherry')



As we have seen in the above examples, we can loop over an iterator with index and element combination as a tuple or directly assigning to two different variables as required in the loop and either to start the counter from default '0' or by specifying the required start position. 

I hope this post has provided a good insight on how to iterate over a list and get index and element from an iterator using 'enumerate' function.


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

Comments

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