On 07/23/2019 10:21 AM, Barry Warsaw wrote:
On Jul 23, 2019, at 09:20, Ethan Furman wrote:
On 07/23/2019 08:44 AM, Steve Dower wrote:
It's trivial, but it adds a runtime overhead that is also trivially avoided by putting the name in __all__ manually. And once it's public API, we shouldn't be making it too easy to rename the function anyway ;)
The run-time overhead added by executing @public is trivially trivial. ;) But your argument about the too-easy change of a public API strikes home.
That actually defeats the purpose of @public IMHO. There should be exactly one source of truth, and that ought to be the @public decorator.
In other words, we should be smart enough to not change the name of the function preceded by an `@public` ? Yeah, I can see that argument, too. ;-) -- ~Ethan~