Skip to main content

String method zfill() in Python

String Method - zfill()

While working with numeric values in a string format, it becomes essential to have the data for a specific length as required i.e., filling the leading blanks with zeros. 

E.g.: If we have number 470 and need to mention this in 5 digits in character format, two leading zeros to be added to make it 5 digits. 

470 --> 00470

String method 'zfill()' is very useful to achieve this. 

Syntax:

str.zfill(width)

Method zfill accepts one argument 'width' which defines the minimum number of digits (width) the return string should be. This method doesn't amend the original string. 

Before we see an example, Below are the few points to consider. 
  • zfill is a string method and cannot be directly used with int or float or other data types. 
  • Width passed as an argument is the minimum number of digits is by considering the period (.) and any prefix (+/-). 
  • If the original string has more width than the width passed in the argument, return string would be same as original string. 
  • No data validation would be done on the string. If the string contains alpha or alphanumeric characters, leading zeros would still be added based on the width passed. 
Let's have a look at few examples to understand this better. 

E.g.: 

Convert the number 470 to a string of 5 digits by appending leading zeros. 

String method zfill() in Python

In the above example, we are doing this in two different ways. 
  • First Method (Line - 2): We are directly mentioning 470 as a string and using the zfill method by passing the width '5' as an argument. This looks easy to understand how zfill works, but we may not be able to do this always and the data tend to change.
  • Second Method (Lines - 6 & 7): We are creating an integer variable by assigning the value 470. And, converting the integer to string by using str() function and using the zfill method on the result. 

The above example is straight forward there are no decimal values or prefixes. So, what would happen if we have decimal values and/or prefixes. 

String method zfill() in Python

In the above example, 
  • Lines - 1 & 2: We are using zfill on the number -470 (prefixed with -, total of 4 digits currently) and the result is '-0470' (only one leading zero is added). Width of the result string is by considering the prefix. 
  • Lines - 5 & 6: We are using zfill on the number -47.0 (prefixed with - and contains ., total of 5 digits currently) and the result is '-47.0' (no change). Current length of the number (converted to string) is same as the width passed, So no change would be done.
Let's have a look at another example where the input number is greater than the width passed. 

String method zfill() in Python

In the above example, both numbers are exceeding the width passed (5) and original string would be returned in this case. 

As mentioned above, No validation would be done on the input string. If alpha or alphanumeric data is passed, zfill would still return a string by appending leading zeros. 

String method zfill() in Python

In the above example, two leading zeros have been added to 'ABC' to return the string of length '5'. 

Hope the above info was useful in understanding the usage of method zfill(). 


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