Скачать или смотреть How to Correctly Attach Poetry Dependencies During Build for a Monorepo Setup

A guide for resolving dependency issues in a Python monorepo using `Poetry`. Learn how to correctly build and run projects without requiring `Poetry` for installation.
---
This video is based on the question https://stackoverflow.com/q/72671290/ asked by the user 'Bob Ross' ( https://stackoverflow.com/u/9911987/ ) and on the answer https://stackoverflow.com/a/72671347/ provided by the user 'Bob Ross' ( https://stackoverflow.com/u/9911987/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

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: How to correctly attach poetry dependencies during build?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Correctly Attach Poetry Dependencies During Build for a Monorepo Setup

Managing dependencies in a Python monorepo can be challenging, especially when using tools like Poetry. If you’re encountering issues attaching dependencies during the build process, you're not alone. In this guide, we'll break down a common problem related to using Poetry in a monorepo structure and provide clear, step-by-step solutions to ensure a seamless build and deployment experience.

The Problem

Imagine you have a monorepo structure consisting of multiple libraries and services. For our example, let's consider the following structure:

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

In the one/main.py file, you're attempting to import and use a function from the notreal library. Your pyproject.toml configuration specifies the necessary dependencies. Here’s the crux of the problem: when you run the command poetry build and later try to install using setup.py, it fails to install the wheel correctly, leading to an "Invalid URL" error.

This issue arises when running the command poetry run python service_one/main.py, which works perfectly but breaks when packaging your application for distribution without Poetry.

Solution Overview

To resolve this issue, we can skip the usage of the setup.py generated by Poetry and directly install the local wheel files. This approach allows you to run your application with Python without relying on Poetry, making it suitable for deployment in environments where Poetry isn't present.

Steps to Implement the Solution

Build the Library: First, we need to build the notreal library to generate the necessary wheel file.

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

This command will produce a file named notreal-0.1.0-py3-none-any.whl in the dist directory.

Copy the Wheel File: After building, copy the generated wheel file to the service’s dist directory manually.

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

Install the Wheel File: Instead of relying on the Poetry-generated setup.py, we will now install the wheel file directly.

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

Run the Application: With the dependency installed, you can run your service as follows:

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

Conclusion

By avoiding the complexities of the Poetry-managed setup.py file and directly handling the installation of the wheel files, you can effectively run your monorepo applications without requiring Poetry in your production environment. This method not only simplifies the deployment process but also ensures that your application remains portable and self-sufficient.

If you're working with a Python monorepo setup and facing similar issues, this approach can greatly enhance your development workflow. Feel free to share your experiences or any additional tips you have for managing dependencies in a monorepo!