1: There are cases where one may need the __name__/__qualname__ of a given callable. If someone uses partial to create a new callable, there is no __name__/__qualname__ given. In my particular case, I'm logging what callback function is passed to a different function... if someone uses partial, there is no __name__/__qualname__ which leads to a current traceback... of course i can work around it but still was an odd case to me.
Per the docs on functools.partial:
"Return a new partial object which when called will behave like func called with the positional arguments args and keyword arguments keywords"
... which made me initially think that in order to behave like the passed in function: it should have __name__ and __qualname__... like the func did.
2: I would say have both __qualname__ and __name__. Both could be based off of __name__/__qualname__ of the passed in func.
3: This would be more difficult since you would have to disassemble the lambda to figure out the called method (or methods)... We can table the lambda discussion for the purpose of this idea. I recall that typically it is preferred to use partial over lambdas, so this could be an additional functionality/benefit of using partial over lambda.
Notes:
... __name__ being something like partial(foo, "x") would be fine with me... I just feel as though something should be there.