can the `pants_version` global option be configure...
# general
h
can the
pants_version
global option be configured to fetch the latest version of pants/master ?
a
in what sense?
it can be, but there's no magic to do that right now
h
I'd like to be able to specify that pants should upgrade itself to the latest version of the codebase on the master git branch (or maybe some arbitrary commit or branch, but right now I care about master)
w
no, it cannot. but master builds do publish wheels to s3
twitter consumes them via
release.sh -p
(ie, building a pex)
and hypothetically you could consume any sha's wheels to run off of nightly.
h
so if I wanted to make my project's pants instance always use the master build, how would I specify it?
(I don't actually want to do this in general, I just want to test against the commit I merged to master a few hours ago. but this seems like a useful thing to be able to do on occasion)
w
Via custom code based on the above
Most likely modifying the venv built by the
pants
script to hit s3