please
please copied to clipboard
High-performance extensible build system for reproducible multi-language builds.
I think we're still compiling with optimisations
If we have a directory with a `.plzconfig`, ideally Please wouldn't try and parse those BUILD files. It should essentially be treated as if it was a blacklisted directory.
`FullPaths` will panic if the file doesn't exist. Rewriting the BuildInput implementation to return errors would probably be better, but I felt it would be overkill for now. This function...
I've allowed plugin authors to define whether some config fields should be inherited from the host repo in #2216 We should do something similar for the non-plugin config values. This...
Compile the please-examples project $ plz build //cc:server Build stopped after 16.12s. 2 targets failed: //cc:_kitten_lib#kitten_cc Error building target //cc:_kitten_lib#kitten_cc: exit status 1 In file included from cc/kitten.cc:1: ./cc/kitten.h, line...
It seems that when switching between test and cover, more is being built than is necessary when no code change has taken place Consecutive invocations of test or cover, yield...
This can probably land in v17
This is just a random idea for now, but adding support for linters would be a nice feature. In a large Go project, using linters currently requires populating the "standard"...
I know that I'm doing something that's against the rules of Please. But I've been doing the same thing in Bazel and it handles this use case well, so maybe...
Having the dependency below: ```python python_wheel(name="prettytable", outs=["prettytable", "prettytable-2.2.1.dist-info"], hashes=["09fb2c7f93e4f93e0235f05ae199ac3f16da3a251b2cfa1c7108b34ede298fa3"], licences=["BSD 3-Clause"], version="2.2.1", deps=[":wcwidth"]) ``` And trying to import the library on a python script results in: ``` Traceback (most recent...