Author steven.daprano
Recipients mjpieters, steven.daprano
Date 2017-08-10.12:18:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1502367525.59.0.249028909687.issue31161@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not sure whether this is a bug or a feature.

In the examples you show, we have *both* an IndentationError/TabError and missing parentheses around print. So I'm almost inclined to say that this is right:

- you get an IndentationError (or TabError);

- and the error message *also* tells you that print is missing parens.

Two errors for the price of one!

I'm not sure that I would have designed it this way from scratch, but given that it already exists I'm not sure that it should be "fixed".

In any case, since the error message itself is not part of the public API, I don't think there's any problem in changing it in a bug-fix release. So *if* we change this, we can change it in 3.6.
History
Date User Action Args
2017-08-10 12:18:45steven.dapranosetrecipients: + steven.daprano, mjpieters
2017-08-10 12:18:45steven.dapranosetmessageid: <1502367525.59.0.249028909687.issue31161@psf.upfronthosting.co.za>
2017-08-10 12:18:45steven.dapranolinkissue31161 messages
2017-08-10 12:18:45steven.dapranocreate