> I suppose you meant to add a third rule > 3) In any branch where a **kwargs -taking function does not call another > function it forwards the **kwargs argument to, it must raise an error if any > unrecognized kwargs are left.
I thought about it for a moment, and wondered if there was any situation were using **kwargs was the right tool in a function that did not forward its input to anything. I couldn't find any. It all seems to boild down to what is being said in other threads: - Don't use **kwargs for whichever arguments are used internally - Use **kwargs for what will be forwarded (and *do* forward it, for the subcall will check that everything is actually read/used inside it) Nathann -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
