Skip to content

Support pylock.toml / PEP 751 requirements files #3088

Closed as duplicate of#2787
Closed as duplicate of#2787
@rickeylev

Description

@rickeylev

With PEP 751 accepted, a new, better, standard (than requirements.txt) for locked requirements is available.

We should support it as an input format for pip.parse et al.

Unfortunately, it's in toml format, so consuming it in Starlark is a bit non-trivial. We either need a Starlark-native toml parser, or a repo-rule phase tool that can convert it to a format for pip.parse to consume (e.g. toml -> json).

Solution ideas:

  1. In pip.parse's repo phase, run a python script to convert toml to json.
  2. Make compile_pip_requirements et al able to produce a JSON equivalent to pylock.toml, which gets fed into pip.parse directly.
  3. Have a prebuilt binary, run during repo phase, convert toml to json
  4. Have a native Starlark parser to parse the toml.

(1) is the simplest, most expedient, solution, but any would suffice.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy