From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 8045 invoked from network); 4 Aug 2023 15:11:09 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 4 Aug 2023 15:11:09 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id BA96342430; Sat, 5 Aug 2023 01:11:05 +1000 (AEST) Received: from mcvoy.com (mcvoy.com [192.169.23.250]) by minnie.tuhs.org (Postfix) with ESMTPS id 7E5874242E for ; Sat, 5 Aug 2023 01:10:55 +1000 (AEST) Received: by mcvoy.com (Postfix, from userid 3546) id 2FBAD35E943; Fri, 4 Aug 2023 08:10:55 -0700 (PDT) Date: Fri, 4 Aug 2023 08:10:55 -0700 From: Larry McVoy To: Dan Cross Message-ID: <20230804151055.GB24315@mcvoy.com> References: <20230803005106.GA12652@mcvoy.com> <20230804010142.GH11023@mcvoy.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Message-ID-Hash: SVTKFFFW6DBIHMJZ7FFI2CQI3BDFQY6Y X-Message-ID-Hash: SVTKFFFW6DBIHMJZ7FFI2CQI3BDFQY6Y X-MailFrom: lm@mcvoy.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: segaloco , tuhs@tuhs.org X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: python List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Fri, Aug 04, 2023 at 11:04:16AM -0400, Dan Cross wrote: > On Thu, Aug 3, 2023 at 9:58???PM Adam Thornton wrote: > > What we've done on my current project is pretty much equivalent to the route Go chose. > > > > Go has go fmt; doesn't matter what you personally believe, just run that pre-commit, and you get a consistent style. For Python we use black. Same idea. It's not what everyone would have chosen--in fact, precisely what it does is not what *anyone* on the project, probably, would have chosen--but the fact is, it does something sane and pretty readable, and then there's no fighting over style. > > This. > > I despised Google's C++ style standards, but I respected them because > they allowed Google to scale to hundreds of millions of lines of C++ > code that was at least intelligible to more or less anyone who worked > there. After a couple of months, people stop noticing the sharp edges > and differences from their personal styles. > > The decades spent arguing over where to put the braces seem wasted, in > retrospect. I can get used to anything, no argument there. I'm teaching my kid some programming and he is eating up my style because I tell him why it is like that. For example, int some_func(int some_arg) { } not int some_func(int some_arg) { } because I can do grep '^some_func(' *.c and find the declaration. I "won" the braces argument by starting my own company and people were pretty happy with the resulting code. --lm