https://pantsbuild.org/ logo
#development
Title
# development
b

busy-vase-39202

10/21/2022, 2:26 AM
Remember when we were bikeshedding a replacement for the
experimental
name and there was a brief digression about bikeshedding BUILD file name? I don't think we ever circled back to that did we?
A nuance to add to that conversation: searching slack or GH issues for issues related to BUILD files is not very helpful because "build" comes up in literally every thread regardless. A more distinctive default name for the files would make it easier for users to identify previous discussions about issues specific to problems related to BUILD files. Wouldn't be 100 accurate, but much less noise.
b

bitter-ability-32190

10/21/2022, 6:12 AM
I would only want a new name so we don't squat with Bazel. My editor keeps thinking BUILD files are for Bazel. Buck uses BUCK,
please
uses BUILD.please I think. Either is fine because it doesn't squat. Users can configure the name, which I think is worthwhile to keep (and still be compatible with BUILD for posterity and for users using both tools). But I think the de-facto being something else would be ideal IMHO
w

wide-midnight-78598

10/21/2022, 10:51 AM
My repos all use
BUILD.pants
, mostly because a lot of my repos use
build
for compilation and output.
If I were being cleverer, I probably would have went with
ZIPPER
or something
b

bitter-ability-32190

10/21/2022, 11:28 AM
(we use BUILD.pants too)
p

proud-dentist-22844

10/21/2022, 1:18 PM
I use
BUILD
simply because that is the default that tailor creates. Vim says
BUILD
files are "filetype=bzl". I've been meaning to change my vim config so it uses "filetype=python" but I haven't got around to it yet, so I often end up typing
:set ft=python
when I open a
BUILD
file.
h

hundreds-father-404

10/21/2022, 1:35 PM
I'd be happy with
BUILD.pants
as the default. If anything, makes it clear to teammates what the hell the file is for
👍 1
w

wide-midnight-78598

10/21/2022, 1:39 PM
If nothing else, then just supporting the default in Pants is a start
build_patterns = ["BUILD.pants", "BUILD"]
I should note that it's also a small pet peeve of mine to have extension-less files that aren't executable.
👆 1
h

hundreds-father-404

10/21/2022, 1:41 PM
yeah, it is supported. The only thing we'd need to change is the default for
tailor
+ our docs. Not sure how to change the default for
tailor
gracefully
w

wide-midnight-78598

10/21/2022, 1:42 PM
Yeah for sure, that's more of a "thing" to consider, not willy-nilly
p

proud-dentist-22844

10/21/2022, 2:27 PM
We would probably need a fixer that updates tailor settings in pants.toml based on which file is present in an existing project. Tailor could even be more adaptive: when there are no
BUILD
files, add the setting to
pants.toml
to make tailor use
BUILD.pants
and then proceed to add the
BUILD.pants
files.
b

busy-vase-39202

10/21/2022, 5:23 PM
I like
BUILD.pants
too, including how it is a declarative little sentence subliminally reminding you you're using Pants now, not Bazel or whatevs.
And eventually it will make a nice visual contrast, to notice Bazel's many heavy
BUILD
files replaced by a handful of lightweight
BUILD.pants
files.