Sharing dev dependencies between projects #3664
Labels
Category: Dependency Resolution
Issue relates to dependency resolution.
Status: Requires PEEP
This issue requires an accompanying enhancement proposal
Type: Behavior Change
This issue describes a behavior change.
Type: Enhancement 💡
This is a feature or enhancement request.
My team has a mondorepo-style setup (single Github repo with several Python projects that are tested, built, and deployed independently). We're looking at using
pipenv
to set each project up with its own Pipfile and virtual-environment, to allow us to isolate project dependencies.At the same time, we want to be able to share a standard set of development dependencies between these projects (e.g.
mypy
,pytest
,autopep8
) to support a standard team development environment. It would appear that our options right now are either:Pipfile
. This isn't very satisfactory because it adds a lot of overhead in keeping those dependencies in sync between projects.pipenv
, e.g. in arequirements.txt
that we install directly viapip
user-install in the system Python. This isn't very satisfactory because it forces us to give up on many of the benefits offered bypipenv
in terms of isolation and repeatability.Is there a recommended setup, using
pipenv
or any other standard tooling, which lets us maintain per-project application dependencies with shared dev dependencies that still gives us isolation and repeatability?The text was updated successfully, but these errors were encountered: