On 3 June 2016 at 08:55, Piotr Duda firstname.lastname@example.org wrote:
2016-06-03 9:45 GMT+02:00 Paul Moore email@example.com:
On 3 June 2016 at 07:05, Steven D'Aprano firstname.lastname@example.org wrote:
I'm objecting to it because it needlessly doubles the number of callables needed. Instead of there being one namedtuple function, you need two: a single parameter version, and a wrapper that performs whatever magic is needed to crowbar the multiple parameter version into the constraint of a single parameter version.
Thanks for clarifying your objection, I hadn't really understood what you had an issue with until now.
OK, so the question is between needing extra callables, vs a somewhat "magical" process for injecting an argument.
We still differ on which is the more acceptable answer, but I'm happy to offer both up for consideration, now that the differences are clear.
There is also third option, return normal object that have special dunder method (ex. __def__), which allow set name (and maybe module and qualname) for object.
Sorry, yes, there may well be other options as well. I haven't been following all of the proposals in this thread. Paul