Skip to content

Change relative path behaviors for requirements files #13239

@zanieb

Description

@zanieb

One part of this is

Similarly, relative paths are relative to the working directory, not the file.

An option...

  • ../<path> to be relative to the file
  • ${PWD}/<path> to be relative to the cwd
  • ${PROJECT_ROOT}/<path> to be relative to the nearest directory with a pyproject.toml, or, if not found, the file
  • ${WORKSPACE_ROOT}/<path> to be relative to the uv workspace root, or, if not found, the file

There are a couple problems here:

  • We need consensus on what it should be
  • We need a way to roll it out
  • We need a way to deal with pip having different behavior

Metadata

Metadata

Assignees

No one assigned

    Labels

    breakingA breaking changeneeds-designNeeds discussion, investigation, or design

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions