Path: ...!feeds.phibee-telecom.net!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.unix.shell,comp.unix.programmer,comp.lang.misc
Subject: Re: Python (was Re: I did not inhale)
Date: Tue, 27 Aug 2024 21:40:19 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 12
Message-ID: <valh42$34s18$2@dont-email.me>
References: <uu54la$3su5b$6@dont-email.me> <v9m4gd$14scu$1@dont-email.me>
	<20240815182717.189@kylheku.com> <v9npls$1fjus$1@dont-email.me>
	<v9t204$2dofg$1@dont-email.me> <va28pi$3dldm$1@dont-email.me>
	<va2ro9$3gd7v$1@dont-email.me> <va2vt0$3h3gj$1@dont-email.me>
	<va44rh$3p1l6$1@dont-email.me> <va45eq$3pkt9$1@dont-email.me>
	<va4aut$3q4g0$1@dont-email.me> <va4fbr$3qvij$1@dont-email.me>
	<va5108$3tmmd$1@dont-email.me> <va51ok$3tqr9$1@dont-email.me>
	<va5ec2$3vluh$1@dont-email.me> <va6q4g$c1a7$1@dont-email.me>
	<va6rpa$c6bg$1@dont-email.me> <va6se9$cb8e$1@dont-email.me>
	<20240826083330.00004760@gmail.com> <vaises$2k7o6$2@dont-email.me>
	<20240826155113.000005ba@gmail.com> <wwvo75eicla.fsf@LkoBDZeT.terraraq.uk>
	<vak9k9$2ujrs$1@dont-email.me> <vakj7g$303sh$1@dont-email.me>
	<20240827080320.00003fd2@gmail.com> <val6u3$33e82$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 27 Aug 2024 23:40:19 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="2836e4fdb00ca78ddad73240b3d2d9a3";
	logging-data="3305512"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/bCNv57dddctUB+zB+S+Pb"
User-Agent: Pan/0.160 (Toresk; )
Cancel-Lock: sha1:n/GugX4j7sb2GeAzS3kp5wsC2Zg=
Bytes: 2512

On Tue, 27 Aug 2024 20:46:27 +0200, David Brown wrote:

> It is not common to have to have indent comment lines (certainly in
> Python it is not necessary).  And if you find yourself writing large
> comments in the middle of a block in the middle of a function, it is
> probably time to consider re-organising the code and/or the comments and
> documentation.  (Again, there can be exceptions to this general rule.)

Counterexample: <https://www.cairographics.org/cookbook/freetypepython/> 
(Yes, that’s one of mine). Note the explanation of the user-data dance, 
for backward compatibility with older FreeType. Where else would you put 
the comments, if not next to the code they’re explaining?