Resolving ModuleNotFoundError: No module named 'markupsafe' in AWS Build Pipeline

Discover how to troubleshoot the `ModuleNotFoundError` for 'markupsafe' when building your Python project in AWS. Learn simple solutions to ensure your pipeline runs smoothly.
---

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: ModuleNotFoundError: No module named in AWS Build

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Troubleshooting ModuleNotFoundError in AWS Build Pipeline

Working with AWS pipelines to build and deploy Python applications can sometimes lead to frustrating errors. One common issue developers encounter is the ModuleNotFoundError, specifically pertaining to the package markupsafe. In this guide, we will explore this problem and provide a straightforward solution to get your project building successfully again.

The Problem: Module Not Found

Recently, a developer faced the following error in their AWS build pipeline:

[[See Video to Reveal this Text or Code Snippet]]

This error occurred despite the project running flawlessly on their local machine. The key points from the developer's experience were:

They were using the project without any recent updates.

The issue persisted even when redeploying an older branch of the code.

The relevant build logs indicated that the issue arose when attempting to install MarkupSafe version 2.1.0, which ultimately failed, leading to the ModuleNotFoundError.

Breakdown of the Error

From the logs shared, it's evident that the error stems from a problem with the installation of the MarkupSafe package during the build process:

Error During Installation: The build system attempted to collect and install MarkupSafe version 2.1.0 from a specified requirements file.

This can often happen when a specific module version isn't compatible with the Python environment settings in AWS.

The Solution: Downgrade MarkupSafe Version

After analyzing the issue, the solution is quite simple—downgrade MarkupSafe to an earlier version that is known to work without any problems. Here’s how to do that:

Step-by-Step Guide

Change the line that specifies MarkupSafe version to:

[[See Video to Reveal this Text or Code Snippet]]

Re-run the Build Pipeline:

This time, the installation should proceed without error, as the older version of MarkupSafe is compatible with your environment.

Benefits of This Approach

Stability: By using a version of MarkupSafe that is known to be stable, you reduce the risk of encountering similar errors in the future.

Speed of Execution: Fixing the version requirement saves time diagnosing or troubleshooting other potential issues that may not directly relate to your current development efforts.

Conclusion

Encountering errors like ModuleNotFoundError: No module named 'markupsafe' can be a real stumbling block when working with AWS build pipelines. However, with a simple intervention—downgrading to MarkupSafe==2.0.1—you can get your project back on track. Always ensure your dependencies are compatible with the environment they're running in to avoid issues down the line.

If you run into any other errors during your development journey, remember that the solution often lies in checking your dependencies and ensuring they align with your environment setup. Happy coding!