(even if you don't actually land the bump... just get things close to green in a branch)

I have learned that by experience now 😉

working on a fix for the error downloading cmake/etc in the bootstrap script on osx mojave. almost finished it earlier but then got hit by a tidal wave of things that weren't at all productive. regardless if you are seeing a 404 when trying to download cmake when developing in the pants repo on 10.14 a workaround is on the way, see the last few comments of https://github.com/pantsbuild/pants/pull/6591

trying to decide whether any automation that helps to avoid users having to remember and consider and debug implementation details like multiple version bumps when upgrading is mathematically possible

https://github.com/pantsbuild/pants/pull/6681 fix for the above

to clarify, this only matters when developing in the pants repo due to the separate rust bootstrap process -- i really have to get around to writing rust support to fix this in general. the original fix which applies to anyone not developing pants as well was done in https://github.com/pantsbuild/pants/pull/6591

is there a way to share a variable across BUILD files ? for example I have a bunch of artefact published with the same organisation and I want to share this value. I tried to add a custom scope in the pants.ini but it does not work directly

do I need to write a plugin for that ?

https://twitter.com/ErbStephan/status/1055419439204700161?s=19 I gave a talk about Pants and PEX at PyCon Germany today. Many people did not know about either and seem to really like what they saw. So hopefully I have generated a few users for you :-) I got a few questions about windows support in PEX and the state of C++ support in Pants. I couldn't really answer either. Can one of you help me out here?

great stuff!

windows would need some (very dedicated) advocates i think... i don't think there has ever been a commit in the direction of adding support there, and there are plenty of unixisms

and re: C/C++ Danny and Chris have done some great work recently to lay groundwork there

i have been developing the new wave of c++ support and python_dist() integration along with @strong-crayon-70379 -- what questions did you receive?

oh stu already said that

@fancy-queen-20734: looks like https://github.com/pantsbuild/pants/pull/6202 is green!

Hey, about publishing I have two Repository: regular & testing. In the BUILD files the provided artifacts are configured to publish on regular. How do I do I want to publish on testing ? do I need to edit the build files ? (the only cli option related to this question I see is

--publish-jar-local

but testing is not local)

Running into some trouble trying to test out a code coverage change i’m attempting…this is the result of running

./pants clean-all test testprojects/tests/java/org/pantsbuild/testproject/unicode/cucumber:: --test-junit-coverage-processor=jacoco --tests-junit-coverage-open --coverage-jacoco-target-filters=Cucumber

look familiar to anyone?

@cuddly-architect-27013: should nuke

~/.cache/pants

probably, sorry!

i think you have veeeery old stuff in there (pre-improved rust version switching)

ok lemme give that a shot…i probably should have guessed that

yeah, note to self: any time an error has “cache” in the message…nuke cache

@enough-analyst-54434 Recent bash to python conversion on release.sh caused some complication for us internally, since it will call now pants thus requiring bootstrap itself via internet. I was wondering if we can just push a pex directly per master SHA to binaires.pantsbuild.org, as it should benefit the community as well to consume any SHA with much lower overhead. We are already doing so per tag, so basically just increasing the frequency there. Thoughts?

I am getting an error when trying to resolve go dependencies and not sure how to resolve the problem. Anyone any idea what path to create to resolve it?

3rdparty/go/github.com/spf13/afero has remote dependencies which require local declaration:
                   	--> <http://golang.org/x/text/unicode/norm|golang.org/x/text/unicode/norm> (expected go_remote_library declaration at 3rdparty/go/golang.org/x/text:unicode/norm)
                   	--> <http://golang.org/x/text/transform|golang.org/x/text/transform> (expected go_remote_library declaration at 3rdparty/go/golang.org/x/text:transform)
                   3rdparty/go/github.com/fsnotify/fsnotify has remote dependencies which require local declaration:
                   	--> <http://golang.org/x/sys/unix|golang.org/x/sys/unix> (expected go_remote_library declaration at 3rdparty/go/golang.org/x/sys:unix)
FAILURE: Failed to resolve transitive Go remote dependencies.

They are the only dependencies where it says it expected a path with a colon => 3rdparty/go/golang.org/x/*sys:unix* I am kind of lost as nothing I tried worked. Is there some magic syntax which I can use? Replace colon with some special char in the path? Couldn't find anything in the docs about it.

Here's an example BUILD for `3rdparty/go/golang.org/x/net:http2`: https://github.com/pantsbuild/pants/blob/master/contrib/go/examples/3rdparty/go/golang.org/x/net/BUILD

The docs in the BUILD dictionary do describe

pkg

but they don't spell out that the pkg forms the target name (the part after the : for all Pants target addresses): https://www.pantsbuild.org/build_dictionary.html

@enough-analyst-54434 Thanks a lot! That resolved my confusion and problem! 🙂

Thinking about reconfiguring project to work with

strict_deps

. Is there a way to have buildgen work with strict dependencies? Maybe by writing to BUILDs suggested missing ones? Maybe it’s not a good idea just thinking on how to manage project with strict dependencies without making engineers manually edit BUILD files

Also, are there any

pantsbuild

meetups in the Bay Area? I feel like I have so many questions about how to properly use pants to efficiently structure projects and effectively use all provided functionality. Other day was looking into

dep-usage

. Very cool tool! Starting to think on how to optimize the structure in terms of usage and minimize the

transitive_cost

. And feel like there are so many more things to discover.

./pants run <python_target>

will produce a pex under dist/, is that intended?