[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Terry J. Reedy added the comment: IDLE's Shell has treated SyntaxWarnings as errors since 2001. I don't know if any other IDE's do the same. Raymond's example did not concern me, as I think not calling known non-callables is preferable. But not executing literal-with-is code, such as "a =

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Serhiy Storchaka added the comment: This is not related to this particular warning, but to how IDLE handles SyntaxWarning. See issue34857. -- assignee: terry.reedy -> components: +Interpreter Core -IDLE status: open -> closed ___ Python tracker

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Serhiy Storchaka added the comment: I think it would be better to open a separate issue for IDLE. -- ___ Python tracker ___ ___

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Raymond Hettinger added the comment: This isn't interacting well with IDLE. --- Works fine at the regular interactive prompt --- $ python3.8 Python 3.8.0b3 (v3.8.0b3:4336222407, Jul 29 2019, 09:46:03) [Clang 6.0 (clang-600.0.57)] on darwin

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Change by Serhiy Storchaka : -- pull_requests: +11960 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Serhiy Storchaka added the comment: New changeset 8e79e6e56f516385ccb761e407dfff3a39253180 by Serhiy Storchaka in branch 'master': Fix syntax warnings in tests introduced in bpo-15248. (GH-11932) https://github.com/python/cpython/commit/8e79e6e56f516385ccb761e407dfff3a39253180 --

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Change by miss-islington : -- pull_requests: +11959 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Change by Serhiy Storchaka : -- pull_requests: +11957 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Serhiy Storchaka added the comment: New changeset 62e4481238b82f111ffb1104a4b97099dd83ae2b by Serhiy Storchaka in branch 'master': bpo-15248: Emit a compiler warning when missed a comma before tuple or list. (GH-11757)

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Change by Serhiy Storchaka : -- pull_requests: +11702, 11703 stage: needs patch -> patch review ___ Python tracker ___ ___

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Change by Serhiy Storchaka : -- pull_requests: +11702 stage: needs patch -> patch review ___ Python tracker ___ ___

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Change by Guido van Rossum : -- nosy: +gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Terry J. Reedy added the comment: I am not sure what you could do at the moment. We have not yet settled whether this is a documentation or interpreter core issue. I posted "Add more SyntaxWarnings?" to pydev to get more comments on Serhiy's patch, especially for other core developers.

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Mayank Singhal <17mayanksing...@gmail.com> added the comment: Hey, if nobody is working on this can I go for it? -- nosy: +storymode7 ___ Python tracker ___

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Serhiy Storchaka added the comment: Actually the precedence was a warning for an assert like: assert(x % 2 == 0, "x is odd") Currently it is the only syntax warning produced by the compiler. > 1. Why 'chech' instead of 'check'? Just a typo replicated with a

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Terry J. Reedy added the comment: Reviewing Serhiy's patch, I changed my mind from 6 years ago (msg164774). I may have over-estimated the difficulty; in any case the code patch is written. (Tests are still needed.) And the code is rather straightforward and readable.

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Serhiy Storchaka added the comment: It is possible to make the compiler producing warnings for such kind of errors. The following sample patch does this. I'm not sure it is worth to do. -- nosy: +serhiy.storchaka ___

[issue15248] Better explain "TypeError: 'tuple' object is not callable"

Change by Serhiy Storchaka : -- keywords: +patch Added file: https://bugs.python.org/file47496/compile-warnings.diff ___ Python tracker

[issue15248] Better explain TypeError: 'tuple' object is not callable

Changes by Ezio Melotti ezio.melo...@gmail.com: -- assignee: - docs@python components: +Documentation keywords: +easy nosy: +docs@python versions: +Python 2.7, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15248

[issue15248] Better explain TypeError: 'tuple' object is not callable

Changes by Terry J. Reedy tjre...@udel.edu: -- stage: - needs patch title: In TypeError: 'tuple' object is not callable, explain that a comma may be missing - Better explain TypeError: 'tuple' object is not callable versions: +Python 3.4 ___ Python