Author terry.reedy
Recipients iter, r.david.murray, terry.reedy
Date 2018-04-21.00:31:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1524270675.32.0.682650639539.issue33274@psf.upfronthosting.co.za>
In-reply-to
Content
It is standard in the Python stdlib that mutation methods usually return None and never echo an input argument.  If one can pass a node to element.removeAttributeNode(node), there is no need to echo it back.  So I suspect that the current behavior is intended.

David, is there a general (perhaps unwritten) rule about how Python translates such functions?

The other 'remove' methods also default to returning None.  Same for the 'set' methods.  All methods would need review before changing just one.
History
Date User Action Args
2018-04-21 00:31:15terry.reedysetrecipients: + terry.reedy, r.david.murray, iter
2018-04-21 00:31:15terry.reedysetmessageid: <1524270675.32.0.682650639539.issue33274@psf.upfronthosting.co.za>
2018-04-21 00:31:15terry.reedylinkissue33274 messages
2018-04-21 00:31:14terry.reedycreate