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

Pants

<https://pypi.org/project/pantsbuild.pants.contrib.buildgen/1.9.0rc0/>

how likely is it that pypi waits a bit before making new releases available?

afaict its guaranteed w/ the new Warehouse backend

just sanity tested by running the "recommended installation" for a new repo, it successfully resolved the pants and contrib plugin versions so running `.../release.sh -t` again

-.txt

looking through the release script to try to debug it now

i suspect this is because i just jumped the gun and there's some local state

```$ pex --disable-cache pantsbuild.pants.contrib.buildgen==1.9.0rc0
Could not satisfy all requirements for pantsbuild.pants.contrib.buildgen==1.9.0rc0:
    pantsbuild.pants.contrib.buildgen==1.9.0rc0```

i was confused because e.g. scrooge is resolved -- but i guess that's the idea since this was published after the scrooge contrib as well

<https://pypi.python.org/simple/pantsbuild-pants-contrib-buildgen/> is the index its hitting

so you could poll that until the new version shows up in release.sh

i also am looking at the post about the warehouse setup so this is less mysterious in the future

i have a bash script that does exponential backoff for an arbitrary command somewhere

<@U6ZRNH0TC> Casual reminder: We’re trying to incrementally rewrite the release script in a real language, rather than adding to the bash :slightly_smiling_face:

yeah libifying that into pants’ bash libs and using it in release.sh would probably make sense to have a single-run process

```[omerta ~]$ curl -sL <https://pypi.org/simple/pantsbuild-pants-contrib-buildgen> | grep 1.9.0rc0
[omerta ~]$```

we can see for sure that the publish worked on the frontend tho: <https://pypi.org/project/pantsbuild.pants.contrib.buildgen/1.9.0rc0/#files>

yeah so that makes me more confident about it