Add python setuptools dependency from specific github commit instead of pypi pa

When working with Python projects, it is common to use dependencies to enhance the functionality of our code. One popular tool for managing dependencies is setuptools, which allows us to easily install and manage external packages. However, sometimes we may need to add a dependency from a specific GitHub commit instead of using the package available on PyPI. In this article, we will explore three different ways to solve this problem.

Option 1: Using the git+ syntax in requirements.txt

The first option is to modify the requirements.txt file of our project to include the GitHub URL of the specific commit. We can do this by using the git+ syntax followed by the URL and the commit hash. Here’s an example:


By specifying the commit hash, we ensure that our project will always use that specific version of the dependency. However, this approach has a downside. If the dependency has any new commits or updates, our project will not automatically receive those changes.

Option 2: Using pip install -e with a local clone

If we want to have the latest changes from the GitHub repository while still using a specific commit, we can use the pip install -e command with a local clone of the repository. Here’s how:

git clone
cd repo
git checkout commit_hash
pip install -e .

This approach creates a local copy of the repository and installs it in editable mode. This means that any changes made to the local clone will be reflected in our project. However, it also means that we need to manually update the local clone if we want to include any new changes from the GitHub repository.

Option 3: Using a dependency manager like Poetry

If we want a more robust and automated solution, we can use a dependency manager like Poetry. Poetry allows us to specify dependencies from specific GitHub commits in a declarative way. Here’s an example:

dependency_name = {git = "", rev = "commit_hash"}

With Poetry, we can easily manage our project’s dependencies and keep them up to date. It also provides other features like virtual environments and dependency resolution. However, using Poetry may require some additional setup and learning curve compared to the previous options.

After exploring these three options, the best choice depends on the specific needs of our project. If we only need a specific commit and don’t expect any updates, option 1 is a simple and straightforward solution. If we want the latest changes while still using a specific commit, option 2 provides more flexibility. Finally, if we want a comprehensive dependency management solution, option 3 with Poetry is the way to go.

Rate this post

7 Responses

  1. Option 1: Using the git+ syntax in requirements.txt sounds like a solid choice but might get messy. What do you think?

  2. Option 3: Using a dependency manager like Poetry seems like a game-changer. Has anyone tried it? Any thoughts?

Leave a Reply

Your email address will not be published. Required fields are marked *

Table of Contents