Skip to content

Support Dev Dependencies #372

Open
Open
@biniona

Description

@biniona

Hi! My name is Alek, and I am interested in using this Buildpack in a tool to create both Development and Production images of an application.

I did a little digging through the codebase (I don't know Rust, so I relied pretty heavily on Claude), and it seems I'm not currently able to override which set of dependencies the Buildpack pulls in (I.E. something like modifying the pip install -r requirements.txt command to pip install -r dev-requirements.txt or modifying the uv sync command to uv sync --group dev).

Would it be possible to add one or more configuration options to this Buildpack to support this feature?

Possible Implementation

If I understand the Buildpack Specification correctly, this could be done through one or more environment variables of the form BP_*.

Would something like this make sense:

BP_PIP_REQUIREMENTS=<file with your requiremnens>
BP_UV_GROUP=<your uv group>

I believe if BP_PIP_REQUIREMENTS was set, then you would need to detect that file to pass detection. If BP_UV_GROUP was set, you would fail detection if uv.lock was missing.

I am unfamiliar with poetry, so I'm unsure what the appropriate mechanism for that tool would be.

PS Hi @edmorley! It was a pleasure meeting you at PyCon!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions