the thrift definition Ny put out uses integers. Right now I'm just storing them in variables like you said

maybe i'll just keep it then

another thing, I tried running all of the tests but it errored out trying to run './pants.pex --python-setup-interpreter-constraints=CPython>=2.7,<3 bash-completion'. Is there a way to fix that?

I used ./build-support/bin/ci.sh to run them

@gorgeous-alligator-94763 ./build-support/bin/ci.sh isn’t recommended to run locally. you can use travis ci to iterate, or

./pants test <targets you changed>

to check your changes

@wide-energy-11069 ohh I totally misunderstood the docs then. Sorry about that! All the targets I changed are passing locally, I just wanted to be sure

Thank you!!

np

Hi all, I have an initial pr out for reporting target info. If/when you have time, could you please take a look? Thank you!! https://github.com/pantsbuild/pants/pull/4561

thanks! will do this evening.

@gorgeous-alligator-94763 Can you point me to the confusing section of the docs that led you to understand that you should use

ci.sh

locally? I’d like to fix that!

the

1.3.0rc0

release is now available! please help to test it, to ensure an excellent and stable

1.3.0

final!: the full set of changes is here: http://www.pantsbuild.org/notes-1.3.x.html

@happy-kitchen-89482 I'm easily confused haha I think I would have been less confused if the sentence "To try all the CI tests in a few configurations, you can run the same script that our Travis CI does" read "To try all the CI tests in a few configurations on your own CI system, you can run the same script that our Travis CI does"

or something like that

Yeah, that sentence is straight-up wrong, sorry about that!

I'm glad I can help lol

added some carrots to the rc0 email: https://groups.google.com/d/topic/pants-devel/z_1Ff2jMKqQ/discussion

Hi. I’ve searched the docs and examples for this and hope i’m missing something obvious: is there any way to use an env var (or arbitrary value from the CLI args) in the build as is possible with most other build tools? I can also live with another “more pants-like” way to deal with this situation: We are open-sourcing some python-based tools that we build with pants. For a few (good, IMO) reasons, there’s a site-specific config file that is statically imported and baked into the binary. This works fine for us, but anyone else building these binaries should be able to put the config file in a repo having any name they like, and that’s where I’m stuck. Is there any way to make the contents of sources [] or dependencies [] variable?

@hallowed-computer-65556 So you’re wanting to publish a separate binary from a pants repo, with different sources / deps? One approach would be to have a separate target for the open source binary, that depends on a different config. You could then put that target in a BUILD file at the same path with a different suffix, if you needed to have them declared in different files.

Not sure I’m parsing that but I’ll read it more carefully in a sec. There’s one dependency - a file with some config values in it - that needs to be in version control, but it’ll be in a repo with a varying name. I would like to ship the open source stuff with a BUILD file that “just works” in that case, apart from the user changing /something/ to indicate where that thing comes from. It’ll be in their private repo. I can’t seem to see a way out w/o passing in a param from the world to the build. The BUILD in the open source bit needs to be in the distribution.

Ah, my suggestion is you have a BUILD file and a BUILD.internal file. In the BUILD file, you have a python_library target containing most of the sources, and a python_binary. The binary would depend on the default, OSS configuration target. In BUILD.internal, you’d have a separate python_binary that depends on the internal config. When publishing the OSS extraction, you skip the BUILD.internal file

also, know that pants consumes any environment variables starting with

PANTS_

to apply to options... so if in your plugin you register an option, you can apply an environment variable to it.

also possible to use

rc

files.

is there some really sophisticated reason that pants doesn’t materialize env vars? Every other build system since the beginning of time has been cool with that

note: I’m ex-twitter and was around when pants was under construction so i’m not unfamiliar with it - just surprised that i can’t do this trivially

@hallowed-computer-65556 : probably because it's python code... if you really want to get at an env var, you can.

in a build file: