Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue #97562 was closed incorrectly. #98619

Closed
aroberge opened this issue Oct 24, 2022 · 2 comments
Closed

Issue #97562 was closed incorrectly. #98619

aroberge opened this issue Oct 24, 2022 · 2 comments
Labels
type-bug An unexpected behavior, bug, or error

Comments

@aroberge
Copy link

In issue #97562, I gave an example showing that code.interact() was giving a SyntaxError whereas the normal Python interpreter was giving a SyntaxWarning. That issue was closed, indicating that a previous commit had essentially fixed it. I cannot reopen a closed issue, but I did add a comment showing that the problem remains. Here's a copy:

> python
Python 3.11.0 (main, Oct 24 2022, 18:26:48) [MSC v.1933 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> def test():
...    [1, 2, 3]()
...
<stdin>:2: SyntaxWarning: 'list' object is not callable; perhaps you missed a comma?
>>> test()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<stdin>", line 2, in test
TypeError: 'list' object is not callable
>>> import code
>>> code.interact()
Python 3.11.0 (main, Oct 24 2022, 18:26:48) [MSC v.1933 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
>>> def test():
...    [1, 2, 3]()
  File "<console>", line 2
SyntaxError: 'list' object is not callable; perhaps you missed a comma?
@aroberge aroberge added the type-bug An unexpected behavior, bug, or error label Oct 24, 2022
@sweeneyde
Copy link
Member

If I'm reading the discussion right, the 3.11 git branch received the fix, commit a386d13, but since we were already in the release candidate phase, in the interest of stability, most changes were not cherry-picked to apply to v3.11.0, and instead will show up in the first bugfix release, 3.11.1.

@aroberge
Copy link
Author

Ok, I wasn't aware of this. I'll monitor changes for 3.11.1, and I'll close this as irrelevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

No branches or pull requests

2 participants