Skip to main content

Calculating the number of business days between dates in Python

Written By: Aryav Nagar


Calculating the number of business days between varying lengths of time, even excluding federal holidays, may seem like a tricky problem to solve, but the solution is quite simple. While developing Stockscast, an AI-based stock market forecaster, I came across this issue as I needed to find the number of days the stock exchange would be open throughout the year. The solution I found involved the use of pandas.tseries.holiday.USFederalHolidayCalendar() and pandas.tseries.offsets.CustomBusinessDay() functions are found in the Pandas library. By creating a custom calendar, using the CustomBusinessDay function, with the frequency of USFederalHolidayCalendar, we can create a calendar excluding both weekends and federal holidays.

Next, find the length of time you want to calculate the number of business days in. In my case, I needed to find the number of business days between one week, one month, three months, six months, and one year from now. Finally, we can utilize our custom calendar to find the number of business days within these periods. By using the pandas.date_range() function, we can find the number of days between our start and end date using a frequency parameter: this would be our business day calendar we declared above. By finding the length of this argument, we can calculate the number of business days present between the start and end dates.


Full code below:


#Import the necessary packages import pandas as pd from pandas.tseries.holiday import USFederalHolidayCalendar from pandas.tseries.offsets import CustomBusinessDay #Other packages required to calculate current date varying time ranges from datetime import date from dateutil.relativedelta import relativedelta #Use the CustomBusinessDay function to create a calendar based on the USFederalHolidayCalendar us_business_days = CustomBusinessDay(calendar=USFederalHolidayCalendar()) #Calculate the dates from varying lengths of time, starting from the current date today = date.today() one_week = date.today() + relativedelta(weeks=+1) one_month = date.today() + relativedelta(months=+1) three_month = date.today() + relativedelta(months=+3) six_month = date.today() + relativedelta(months=+6) one_year = date.today() + relativedelta(years=+1) #Find the number of business days from your start date to your end date using a frequency of the us_business_days calendar (declared above) one_week_business_days = len(pd.date_range(start=today,end=one_week, freq=us_business_days)) one_month_business_days = len(pd.date_range(start=today,end=one_month, freq=us_business_days)) three_month_business_days =len(pd.date_range(start=today,end=three_month, freq=us_business_days)) six_month_business_days = len(pd.date_range(start=today,end=six_month, freq=us_business_days)) one_year_business_days = len(pd.date_range(start=today,end=one_year, freq=us_business_days))


Comments

Popular posts from this blog

React - Uncaught TypeError: destroy is not a function

Written by Aryan Mittal While experimenting with useEffect hooks in React and React Native, I came across the following error: Uncaught TypeError: destroy is not a function and my app was unable to run. After debugging and searching around, I found the cause and how to solve it. A simplified version of my code looked like this: The key here is that myFunction is async and the shorthand arrow function syntax I used. The reason the simple code above was crashing my app is due to how the useEffect hook, async functions, and the shorthand arrow function syntax works. One feature of the useEffect hook is a cleanup function. If you return anything from the useEffect hook function, it must be a cleanup function. This function will run when the component unmounts. This can be thought of as roughly equivalent to the componentWillUnmount lifecycle method in class components. In JavaScript, functions marked with the async keyword enable the use of the await feature, which lets developers paus

AWS vs. Google Cloud Services: Which one should you use?

Which is the better option?  Written by Siddhanth Kumar The database is a crucial component of most modern software applications. A database allows you to store and manage information in a table format. Moreover, database systems can be hosted on dedicated servers in the cloud, allowing anybody to access them from their local machine. A cloud database can open up opportunities for account systems due to user information being associated with their credentials rather than being stored locally. Luckily, developers are in luck! Big tech companies have created cloud-based database services to allow developers to use databases without too much hassle and personal setup. For developers currently looking to use a cloud database service, two major options exist Google’s Firebase and Amazon Web Services (AWS) DynamoDB. In this article, I’ll be reviewing 3 of the most database-related tasks necessary for most modern applications and compare AWS services against Google Cloud Services. User A

What’s New in React 17: No New Features?

  What’s New in React 17: No New Features? Written by Aryan Mittal Over two years after React 16 was launched, the long-awaited React 17 was released in October 2020. While the update introduced numerous great changes as always, this release is unique because it contains no new developer-facing features. While React 16 added significant features like Hooks and the Context API, React 17 is mostly considered a stepping stone to ease the transition to future releases. More specifically, the primary purpose of the update was to enable gradual React upgrades. When you upgrade from React 15 to 16 (or, this time, from React 16 to 17), you would usually upgrade your whole app at once. This works well for many apps, but it can get increasingly challenging if the codebase was written more than a few years ago and isn’t actively maintained. And while it’s possible to use two versions of React on the page, until React 17 this has been fragile and caused problems with events. The React team has fix