I am probably missing something obvious here. My PEX files depend transitively on the requirements.txt file, and they are rebuilt even if the change does not affect the code inside them. I was expecting the dependencies to be on specific entries in the requrements file. Why does it depend on the whole file? On second thought, maybe the problem is the dependency on the lockfile... That would make more sense. I wish there was a way to not rebuild (and redeploy) everything whenever some dependency is changed.

That dep is necessary for change detection - if requirements.txt changes, and you're using the

--changed-*

flags we must attempt to rebuild. But you should be getting cached results in practice?

Oh, yes, I see. The thing is that I use --changed-since to decide if a pex or docker image needs to be deployed. I don't want to deploy an identical binary. I guess that sometimes I have to live with that.

Yeah, that part needs some work. There are some open tickets about supporting smart versioning of a binary in that way.