Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

<@U04S45AHA>: Thanks. <@U06A03HV1> were you guys affected by this?

Got an error trying to test plugins in our repo that had pantsbuild.pants.testinfra dependencies: `Could not satisfy all requirements for six&gt;=1.4:`

(it's been almost a month since our last internal release)

It would only affect a pants repo containing pants extensions

We didn’t do a release, six did, and that broke us

For twitter that's - used to - bot be the main monorepo

whatever solution we settle on for jvm 3rdparty, would be good to share infra with our python solution

Like node, the deps in the 3rdparty universe float

so even if you pin, need more fancy intervention if you allow resolves

they exist - I've seen at least 2 that I recall

I’ve been working on this: <https://github.com/pantsbuild/pants/issues/2320> It seems that in cache_setup.py,  read_cache_available() returns True if a cache is configured. It doesn’t actually check that that cache is reachable. Adding the check slows everything right down. Without the check, a configured, but unreachable cache causes the build to fail.

I’m not quite sure what the solution is here. A cache of caches so checking doesn’t take so long?

we've been interested in doing cache speculation for a while

such that you attempt to hit the cache AND compute the result in parallel. will likely not be feasible until after the engine refactor

<@U04S45AHA>: except <https://github.com/pantsbuild/pants/issues/2329> , which is basically exactly a "resolve everything up front and stabilize" approach

<https://pypi.python.org/pypi/pantsbuild.pants/0.0.52>

<@U098KD4HJ>: <@U098ZNTCN> is also interested in this; i think it boils down to re-resolving the cache periodically to decide whether it is worth using

thanks :simple_smile: Keep telling everyone else that :simple_smile: