Lines Matching full:pip

15 "pip module extension for use with bzlmod"
41     """Implementation of the pip.whl_mods tag class.
81             SimpleAPI evaluating all of the tag class invocations {bzl:obj}`pip.parse`.
124                 "Unable to find interpreter for pip hub '{hub_name}' for " +
285                         # pip is not used to download wheels and the python
287                         # for sdists, they will be built by `pip`, so we still
291                     # This is no-op because pip is not used to download the wheel.
324 …logger.warn(lambda: "falling back to pip for installing the right file for {}".format(requirement.…
427     # Used to track all the different pip hubs and the spoke pip Python
433     # dict[hub, dict[whl, dict[version, str pip]]]
434     # Where hub, whl, and pip are the repo names
455                     "Duplicate cross-module pip hub named '{hub}': pip hub " +
467                     "Duplicate pip python version '{version}' for hub " +
539 …"""Implementation of a class tag that creates the pip hub and corresponding pip spoke whl reposito…
541     This implementation iterates through all of the `pip.parse` calls and creates
542     different pip hub repositories based on the "hub_name".  Each of the
543     pip calls create spoke repos that uses a specific Python interpreter.
547     pip.parse(
548         hub_name = "pip",
553     pip.parse(
554         hub_name = "pip",
560     For instance, we have a hub with the name of "pip".
562     all of the pip spokes are collected.
564     - @@rules_python~override~pip~pip
567     Two different pip.parse statements exist in MODULE.bazel provide the hub_name "pip".
568     These definitions create two different pip spoke repositories that are
569     related to the hub "pip".
572     Both of these pip spokes contain requirements files that includes websocket
575     We also need repositories for the wheels that the different pip spokes contain.
577     each pip spoke had a requirements file that contained websockets. We
580     - @@rules_python~override~pip~pip_39_websockets
581     - @@rules_python~override~pip~pip_310_websockets
589     hubs pointing to various different pip spokes.
592     have a hub named "pip" that has two spokes that use the Python 3.9 interpreter.  Second
637     """Get the attributes for the pip extension.
655 This is equivalent to `--extra-index-urls` `pip` option.
671 This is equivalent to `--index-url` `pip` option.
674 If {attr}`download_only` is set, then `sdist` archives will be discarded and `pip.parse` will
699 The name of the repo pip dependencies will be accessible from.
703 in the hub name. Repo mapping, `use_repo(..., pip="my_modules_pip_deps")`, can
707 versions of pip dependencies under one repository name. This allows using a
708 Python version-agnostic name when referring to pip dependencies; the
711 Typically, a module will only have a single hub of pip dependencies, but this
712 is not required. Each hub is a separate resolution of pip dependencies. This
800 pip.parse. If you have different pip hubs you can use a different name,
828 applied to all repositories that setup this distribution via the pip.parse tag
852 This extension is used to make dependencies from pip available.
854 pip.parse:
855 To use, call `pip.parse()` and specify `hub_name` and your requirements file.
859 Each `pip.parse()` call configures a particular Python version. Multiple calls
861 the `hub_name` argument. This allows the same logical name, e.g. `@pip//numpy`
864 pip.whl_mods:
874 This tag class is used to create a pip hub and all of the spokes that are part of that hub.