Ah, looks like the patch implements #2, adding a return value and using it, which does not break compatibility with the old API. Without a custom name chooser, an exception appears as if it would be raised.
+1 to that.
Ah, looks like the patch implements #2, adding a return value and using it, which does not break compatibility with the old API. Without a custom name chooser, an exception appears as if it would be raised.
+1 to that.