This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Anthony Sottile
Recipients Anthony Sottile, mbussonn, serhiy.storchaka
Date 2019-05-15.16:29:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The simplest case is just the addition of an `isinstance` check:

class V(ast.NodeVisitor):
    def visit_Str(self, node):

    def visit_Constant(self, node):
        if isinstance(node.value, str):

But I have another case where there's much more complex (sorry this one's private, I'll give the pseudo-code of it though which ends up in a whole mess of slow `isinstance(...)` calls

class V(ast.NodeVisitor):
    def visit_Str(self, node):

    def visit_Bytes(self, node):

    def visit_Num(self, node):

    def visit_Constant(self, node):
        if isinstance(node.value, str):
             return self.visit_Str(node)
        # Annoying special case, bools are ints, before this wouldn't call
        # `visit_Num` because there was a separate `visit_NameConstant` for `True` / `False`
        elif isinstance(node.value, int) and not isinstance(node.value, bool):
            return self.visit_Num(node)
        elif isinstance(node.value, bytes):
            return self.visit_Bytes(node)
            return self.generic_visit(node)

Whereas the opposite case (where handling all constants the same) is much much easier to simplify the code and not need the `Constant` mess (if required)

class V(ast.NodeVisitor):
    def _visit_constant(self, node):
        # generic handling of constant _if you want it_

    visit_Str = visit_Num = visit_Bytes = visit_NameConstant = visit_Ellipsis = _visit_constant

Maybe I haven't been in the community long enough but this is the first *removal* of the ast I've seen, and it makes all my uses of these functions objectively worse, and none of the cases get simpler (whereas there's an existing easy way to simplify constants already, without breaking the ast)

github search isn't a great measure of this but it's currently showing 10k+ usages of `visit_{Str,Num,Bytes}` that would presumably be broken by this change: -- backward compatibility is very valuable, I would hope it isn't squandered for an internal cleanup
Date User Action Args
2019-05-15 16:29:19Anthony Sottilesetrecipients: + Anthony Sottile, serhiy.storchaka, mbussonn
2019-05-15 16:29:19Anthony Sottilesetmessageid: <>
2019-05-15 16:29:19Anthony Sottilelinkissue36917 messages
2019-05-15 16:29:19Anthony Sottilecreate