Deriving a `py_wheel`'s pinned `requires` from the lock

[azryve]

We've got a Bazel monorepo with all external python deps managed by ofiuco - one pyproject.toml + lock for the whole repo.
Works great for the usual py_binary /py_library case: targets just depend on @poetry//:<pkg> and it all resolves from the lock.

Some of our client-side tools I'd like to ship as wheels built with py_wheel. I don't particularly want to vendor deps into those wheels (size), so I list them as pinned runtime requirements (requires / Requires-Dist) - a subset of what's already in our lock.

So the annoying part that requirements list duplicates stuff the lock already knows - the names and the pinned versions.
I have to keep it in sync by hand, so it drifts (stale versions end up in the published wheel) and I're maintaining name/version in two places.

Example

# Direct deps pins copied by hand from the pyproject lock
requirements = [
    "dep-a==1.2.3",
    "dep-b==0.9.0",
    "dep-c==1.33",
    # ...
]

# Strip version + add the ofiuco repo to get the library deps
poetry_requirements = [
    "@poetry//:" + x.split("=")[0]
    for x in requirements
]

py_library(
    name = "mytool_core",
    srcs = glob(["mytool_core/**/*.py"]),
    visibility = ["//:__subpackages__"],
    deps = poetry_requirements,
)

py_package(
    name = "mytool_pkg",
    packages = ["myorg.mytool"],
    deps = [":mytool_core"],
)

py_wheel(
    name = "mytool_core_wheel",
    distribution = "mytool_core",
    entry_points = {
        "console_scripts": ["mytool = myorg.mytool.mytool_core.main:main"],
    },
    platform = "any",
    python_tag = "py3",
    requires = requirements,
    deps = [":mytool_pkg"],
)

Before I go build something: is there already a way (or a recommended pattern) in ofiuco to get a py_wheel's pinned requires straight from the lock, instead of copying the pins by hand? Just want to make sure I'm not reinventing the wheel here.

Thank you.

[oxidase]

Hey, ofiuco has no such feature, would be nice to have and it is not complicated to add: additionally to BUILD.bazel in the repository add defs.bzl file with

requirements = [
{{ deps }}
]

which can be loaded later in your project.

Lock files parsed at rule https://github.com/oxidase/ofiuco/blob/bd4caf83/python/extensions.bzl#L22
Python script called at https://github.com/oxidase/ofiuco/blob/bd4caf83/python/private/lock_parser.bzl#L20-L28
and defs.bzl can be written after https://github.com/oxidase/ofiuco/blob/d10b3a19/python/private/lock_parser.bzl#L33

Push a request if you find it useful, otherwise I can add an example on the weekend.

[azryve]

Hi. Thank you, yes I would appreciate an example of your approach.

During the weekend my train of thought was drifting toward this kind of interface but I am not sure if its a good fit:

py_library(
    name = "applib",
    srcs = ["app.py"],
    deps = [
        "@poetry//:requests",
        "@poetry//:urllib3[brotli]",
    ],
)

py_binary(
    name = "app",
    srcs = ["app.py"],
    main = "app.py",
    deps = [":applib"],
)

# Walks the binary's direct ofiuco dependencies (descending through :applib but not
# into ofiuco's package->package graph), pins each to the version in poetry.lock and
# writes a requirements file.
py_requires_file(
    name = "app_requires",
    repo = "@poetry",
    target = ":app",
)

py_wheel(
    name = "app_wheel",
    distribution = "app",
    python_tag = "py3",
    requires_file = ":app_requires",
    version = "0.0.1",
    deps = [":app"],
)

[oxidase]

Hey, I've added an example in #136 @azryve pls could you check if it works for your use case, if so i'll merge and cut a release.

[azryve]

Hi Michael. I tried in our repo and it seems to work. I will play with it a bit more but thank you for such a quick implementation.