Hi guys! I am wondering is there some best practice guide or tutorial specifically for python projects? I am in the process of optimizing our pantsbuilds for the CI and had the misconception that the remote cache is caching the same as without. It seems many things are only cached in pants.d. Would love to read more about caching in pants.

Unfortunately, not much of the python stack uses the remote cache yet; so you're observation is correct. Right now there is no documentation of which tasks use the remote cache. In the python stack it's currently only test results that can be cached.

is there anything specific in the python stack which would clearly lend itself to use of a remote cache and isn't right now?

For example remote dependencies also dependencies which have to be build?

ah, of course, sorry. especially dependencies that have to be built is something we haven't addressed internally at twitter but might be soon, because we want to have some python binaries available transparently on linux and osx. the v2 engine interacts with a remote process execution API that (if the task is defined with a v2 rule) ends up giving you remote caching without even trying -- and we are definitely going to be expanding the v2 python pipeline soon, so there may be change in this area soon. until then, using a remote cache might require writing a good amount of code yourself ):

Thanks @aloof-angle-91616! Sounds good!