forked from bazelbuild/rules_python
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
refactor: don't load repo-phase objects from build-phase (bazelbuild#…
…2056) As a general practice, the repo-phase and build-phase shouldn't load code from one another because they can't use each other's objects. It can also result in confusing behavior because the "starlark environment" is slightly different between the two phases. Additionally, Google's version of Bazel essentially disables repo-phase objects, so loading e.g. http_archive results in errors. This makes it more difficult to import rules_python into Google, as we have to maintain patches to cut out the code (and thus we spend more time trying to import the code than working on it).
- Loading branch information
Showing
4 changed files
with
22 additions
and
28 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters