pants peek

outputs the sources fingerprint, but I would be much interested in the dependencies fingerprint too. Is it possible to obtain this?

I agree that I’d be nice to have. The fingerprint of the dependencies is slightly awkward to define, though. For instance, the raw fingerprints of the files on disk via filedeps captures “normal” python_source -> python_source dependencies, but doesn’t work well if there’s a dependencies on some code-generation (like

shell_command

). In that case, the BUILD target’s fields matter too, because they’ll influence the codegen output. In the general case the pants.toml options can change things too. That is to say, if you’re in a constrained situation, a shell pipeline like your idea is reasonable, but a fully general solution built into pants itself is harder 😦