Path: csiph.com!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: Lawrence =?iso-8859-13?q?D=FFOliveiro?= Newsgroups: comp.lang.python Subject: Re: staticmethod(cls) Date: Fri, 5 Sep 2025 00:15:10 -0000 (UTC) Organization: A noiseless patient Spider Lines: 12 Message-ID: <109da2e$2344i$4@dont-email.me> References: <109cp9l$f41$1@reader1.panix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Fri, 05 Sep 2025 00:15:10 +0000 (UTC) Injection-Info: dont-email.me; posting-host="61d33da926bd3da628ada3a545383748"; logging-data="2199698"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+mO+Lv4S98+EIMM9tgmOhs" User-Agent: Pan/0.163 (Kryvyi Rih) Cancel-Lock: sha1:BuD/jSforWucUk5KzS3ueyQr8nw= Xref: csiph.com comp.lang.python:197555 On Thu, 4 Sep 2025 19:28:53 -0000 (UTC), Pierre Asselin wrote: > Now that's *seriously* not-in-the-manual. I won't rely on that > behavior, plus the expanded documentation is a bit too much, > but I'm curious as how that interaction between staticmethod() > and help()/pydoc came about. Note that the help for Inner1 is listed in the section of the help for Outer headed “Static methods defined here:”. So all that’s happening is that the help() function is looking for class members that have been put through staticmethod(), whatever their type is, and I think recursively putting them through their own help() calls.