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 o11c
Recipients o11c
Date 2012-07-04.05:28:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1341379722.78.0.0866285571225.issue15248@psf.upfronthosting.co.za>
In-reply-to
Content
I frequently construct lists of tuples, such as:
[
  (1, 2, 3) # oops, missing comma!
  (4, 5, 6)
]

It would be nice if the error message gave a hint on what was *actually* wrong.

Although I always use homogeneous containers, the type that's not callable could be something other than 'tuple'.

You could possibly cut down on false positives (at the risk of false negatives) by checking that the not-callable object is newly constructed.

A better way to cut down on false positives would be to check that a list, tuple, or set is being constructed from a literal, but this might be more complex.
History
Date User Action Args
2012-07-04 05:28:42o11csetrecipients: + o11c
2012-07-04 05:28:42o11csetmessageid: <1341379722.78.0.0866285571225.issue15248@psf.upfronthosting.co.za>
2012-07-04 05:28:42o11clinkissue15248 messages
2012-07-04 05:28:41o11ccreate