gh-128231: Use `runcode()` return value for failing early #129488

bswck · 2025-01-30T23:01:22Z

Any potential downstream subclasses (which are hard to imagine, but who knows, Python is big) that override runcode() can introduce this protocol gradually, with the old behavior preserved until then (backward compatibility).

Issue: In the new REPL, multiline input execution should fail fast #128231

bswck · 2025-01-30T23:05:11Z

Should we document the new sentinel? It seems the InteractiveColoredConsole class isn't documented anywhere.

Eclips4 · 2025-01-31T20:24:49Z

Should we document the new sentinel? It seems the InteractiveColoredConsole class isn't documented anywhere.

I don't think that we should document it.

Eclips4

LGTM. Thank you

Lib/_pyrepl/console.py

bswck · 2025-02-12T15:04:00Z

@encukou (Pinging as discussed on stream)

ZeroIntensity

Might as well throw my approval on here too. I think this makes sense.

bswck · 2025-02-13T01:54:09Z

Will also ping @asvetlov as he had reviewed my first PR, relevant to the (asyncio) REPL.

encukou · 2025-02-14T14:03:47Z

This makes sense to me!
Perhaps STATEMENT_FAILED is not the ideal API, but it's contained to private subclasses.

I'll give a chance to the REPL experts to review, but if there are no objections next week I plan to merge this.

miss-islington-app · 2025-02-24T14:50:27Z

Thanks @bswck for the PR, and @encukou for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13.
🐍🍒⛏🤖

…onGH-129488) (cherry picked from commit 7ed3dc6) Co-authored-by: Bartosz Sławecki <[email protected]>

bedevere-app · 2025-02-24T14:50:37Z

GH-130513 is a backport of this pull request to the 3.13 branch.

…129488) (#130513) gh-128231: Use `runcode()` return value for failing early (GH-129488) (cherry picked from commit 7ed3dc6) Co-authored-by: Bartosz Sławecki <[email protected]>

bedevere-bot · 2025-03-28T11:19:09Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot AMD64 CentOS9 NoGIL 3.13 (tier-1) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1608/builds/601) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1608/builds/601

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.13.itamaro-centos-aws.nogil/build/Lib/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ experimental free-threading build (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 11:15:04) [GCC 11.5.0 20240719 (Red Hat 11.5.0-5)] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.itamaro-centos-aws.nogil/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/home/buildbot/buildarea/3.13.itamaro-centos-aws.nogil/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/home/buildbot/buildarea/3.13.itamaro-centos-aws.nogil/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.itamaro-centos-aws.nogil/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/home/buildbot/buildarea/3.13.itamaro-centos-aws.nogil/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/home/buildbot/buildarea/3.13.itamaro-centos-aws.nogil/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

bedevere-bot · 2025-03-28T11:23:35Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot ARM64 MacOS M1 NoGIL 3.13 (tier-2) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1408/builds/1023) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1408/builds/1023

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-arm64-aws.macos-with-brew.nogil/build/Lib/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ experimental free-threading build (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 11:16:47) [Clang 15.0.0 (clang-1500.0.40.1)] on darwin\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-arm64-aws.macos-with-brew.nogil/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-arm64-aws.macos-with-brew.nogil/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-arm64-aws.macos-with-brew.nogil/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-arm64-aws.macos-with-brew.nogil/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-arm64-aws.macos-with-brew.nogil/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-arm64-aws.macos-with-brew.nogil/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

ZeroIntensity · 2025-03-28T11:23:50Z

Uh oh, that looks related. Should we revert the 3.13 PR @hugovk?

bedevere-bot · 2025-03-28T11:29:42Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot AMD64 FreeBSD 3.13 (tier-3) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1491/builds/1057) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1491/builds/1057

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/buildbot/buildarea/3.13.ware-freebsd/build/Lib/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 06:23:23) [Clang 18.1.6 (https://github.com/llvm/llvm-project.git llvmorg-18.1.6-0-g1118c2 on freebsd13\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/buildbot/buildarea/3.13.ware-freebsd/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/buildbot/buildarea/3.13.ware-freebsd/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/buildbot/buildarea/3.13.ware-freebsd/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/buildbot/buildarea/3.13.ware-freebsd/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/buildbot/buildarea/3.13.ware-freebsd/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/buildbot/buildarea/3.13.ware-freebsd/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

bedevere-bot · 2025-03-28T11:36:41Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot ARM64 macOS 3.13 (tier-2) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1404/builds/828) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1404/builds/828

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/Users/buildbot/buildarea/3.13.pablogsal-macos-m1.macos-with-brew/build/Lib/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 11:28:40) [Clang 16.0.0 (clang-1600.0.26.4)] on darwin\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/Users/buildbot/buildarea/3.13.pablogsal-macos-m1.macos-with-brew/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/Users/buildbot/buildarea/3.13.pablogsal-macos-m1.macos-with-brew/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/Users/buildbot/buildarea/3.13.pablogsal-macos-m1.macos-with-brew/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/Users/buildbot/buildarea/3.13.pablogsal-macos-m1.macos-with-brew/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/Users/buildbot/buildarea/3.13.pablogsal-macos-m1.macos-with-brew/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/Users/buildbot/buildarea/3.13.pablogsal-macos-m1.macos-with-brew/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

bedevere-bot · 2025-03-28T11:37:15Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot AMD64 Windows Server 2022 NoGIL 3.13 (tier-1) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1488/builds/1128) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1488/builds/1128

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "C:\Users\Administrator\buildarea\3.13.itamaro-win64-srv-22-aws.x64.nogil\build\Lib\test\test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ experimental free-threading build (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 11:25:43) [MSC v.1943 64 bit (AMD64)] on win32\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "C:\\Users\\Administrator\\buildarea\\3.13.itamaro-win64-srv-22-aws.x64.nogil\\build\\Lib\\concurrent\\futures\\_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "C:\\Users\\Administrator\\buildarea\\3.13.itamaro-win64-srv-22-aws.x64.nogil\\build\\Lib\\concurrent\\futures\\_base.py", line 401, in __get_result\n    raise self._exception\n  File "C:\\Users\\Administrator\\buildarea\\3.13.itamaro-win64-srv-22-aws.x64.nogil\\build\\Lib\\asyncio\\__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "C:\\Users\\Administrator\\buildarea\\3.13.itamaro-win64-srv-22-aws.x64.nogil\\build\\Lib\\runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "C:\\Users\\Administrator\\buildarea\\3.13.itamaro-win64-srv-22-aws.x64.nogil\\build\\Lib\\runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "C:\\Users\\Administrator\\buildarea\\3.13.itamaro-win64-srv-22-aws.x64.nogil\\build\\Lib\\asyncio\\__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \nC:\\Users\\Administrator\\buildarea\\3.13.itamaro-win64-srv-22-aws.x64.nogil\\build\\Lib\\asyncio\\base_events.py:758: ResourceWarning: unclosed event loop <ProactorEventLoop running=False closed=False debug=False>\n'

bedevere-bot · 2025-03-28T11:39:24Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot x86 Debian Installed with X 3.13 (no tier) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1398/builds/1056) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1398/builds/1056

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/buildbot/buildarea/3.13.ware-debian-x86.installed/build/target/lib/python3.13/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 06:34:22) [GCC 12.2.0] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/buildbot/buildarea/3.13.ware-debian-x86.installed/build/target/lib/python3.13/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/buildbot/buildarea/3.13.ware-debian-x86.installed/build/target/lib/python3.13/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/buildbot/buildarea/3.13.ware-debian-x86.installed/build/target/lib/python3.13/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "<frozen runpy>", line 198, in _run_module_as_main\n  File "<frozen runpy>", line 88, in _run_code\n  File "/buildbot/buildarea/3.13.ware-debian-x86.installed/build/target/lib/python3.13/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

bedevere-bot · 2025-03-28T11:45:39Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot AMD64 FreeBSD14 3.13 (tier-3) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1481/builds/1086) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1481/builds/1086

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.13.opsec-fbsd14/build/Lib/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 12:33:55) [Clang 18.1.6 (https://github.com/llvm/llvm-project.git llvmorg-18.1.6-0-g1118c2 on freebsd14\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.opsec-fbsd14/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/home/buildbot/buildarea/3.13.opsec-fbsd14/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/home/buildbot/buildarea/3.13.opsec-fbsd14/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.opsec-fbsd14/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/home/buildbot/buildarea/3.13.opsec-fbsd14/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/home/buildbot/buildarea/3.13.opsec-fbsd14/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

bedevere-bot · 2025-03-28T11:45:42Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot x86 Debian Non-Debug with X 3.13 (no tier) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1389/builds/1066) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1389/builds/1066

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/buildbot/buildarea/3.13.ware-debian-x86.nondebug/build/Lib/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 06:40:14) [GCC 12.2.0] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/buildbot/buildarea/3.13.ware-debian-x86.nondebug/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/buildbot/buildarea/3.13.ware-debian-x86.nondebug/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/buildbot/buildarea/3.13.ware-debian-x86.nondebug/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "<frozen runpy>", line 198, in _run_module_as_main\n  File "<frozen runpy>", line 88, in _run_code\n  File "/buildbot/buildarea/3.13.ware-debian-x86.nondebug/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

bedevere-bot · 2025-03-28T11:49:46Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot x86-64 MacOS Intel ASAN NoGIL 3.13 (tier-1) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1460/builds/1024) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1460/builds/1024

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.macos-with-brew.asan.nogil/build/Lib/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ experimental free-threading build (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 11:37:17) [Clang 14.0.3 (clang-1403.0.22.14.1)] on darwin\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.macos-with-brew.asan.nogil/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.macos-with-brew.asan.nogil/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.macos-with-brew.asan.nogil/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "<frozen runpy>", line 198, in _run_module_as_main\n  File "<frozen runpy>", line 88, in _run_code\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.macos-with-brew.asan.nogil/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

bedevere-bot · 2025-03-28T11:56:41Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot AMD64 Debian root 3.13 (tier-1) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1441/builds/1025) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1441/builds/1025

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 22:41:51) [GCC 12.2.0] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'


Traceback (most recent call last):
  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 22:41:51) [GCC 12.2.0] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/concurrent/futures/_base.py", line 449, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

bedevere-bot · 2025-03-28T12:01:14Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot x86-64 MacOS Intel NoGIL 3.13 (tier-1) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1449/builds/1031) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1449/builds/1031

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.nogil/build/Lib/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ experimental free-threading build (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 11:51:41) [Clang 14.0.3 (clang-1403.0.22.14.1)] on darwin\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.nogil/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.nogil/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.nogil/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.nogil/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.nogil/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.nogil/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

bedevere-bot · 2025-03-28T12:02:33Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot s390x RHEL8 3.13 (tier-3) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1469/builds/847) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1469/builds/847

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x/build/Lib/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 07:58:39) [GCC 8.5.0 20210514 (Red Hat 8.5.0-24)] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

hugovk · 2025-03-28T12:10:27Z

The 3.13 backport is failing GHA and buildbots, it must have gotten out of sync between last CI run and merge.

Let's revert the 3.13 backport to get the CI back to green.

Edit: revert PR #131834

bedevere-bot · 2025-03-28T12:15:10Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot s390x RHEL8 LTO + PGO 3.13 (tier-3) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1436/builds/849) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1436/builds/849

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto-pgo/build/Lib/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 08:09:27) [GCC 8.5.0 20210514 (Red Hat 8.5.0-24)] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto-pgo/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto-pgo/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto-pgo/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "<frozen runpy>", line 198, in _run_module_as_main\n  File "<frozen runpy>", line 88, in _run_code\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto-pgo/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

…ing early (pythonGH-129488) (python#130513)" This reverts commit 8f6a9aa.

bedevere-bot · 2025-03-28T12:19:42Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot s390x RHEL9 3.13 (tier-3) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1584/builds/566) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1584/builds/566

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x/build/Lib/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 07:16:03) [GCC 11.5.0 20240719 (Red Hat 11.5.0-5)] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

bedevere-bot · 2025-03-28T12:21:57Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot s390x RHEL8 LTO 3.13 (tier-3) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1458/builds/853) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1458/builds/853

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto/build/Lib/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 08:15:50) [GCC 8.5.0 20210514 (Red Hat 8.5.0-24)] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "<frozen runpy>", line 198, in _run_module_as_main\n  File "<frozen runpy>", line 88, in _run_code\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

bedevere-bot · 2025-03-28T12:33:53Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot s390x RHEL9 LTO + PGO 3.13 (tier-3) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1574/builds/566) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1574/builds/566

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto-pgo/build/Lib/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 07:28:25) [GCC 11.5.0 20240719 (Red Hat 11.5.0-5)] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto-pgo/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto-pgo/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto-pgo/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "<frozen runpy>", line 198, in _run_module_as_main\n  File "<frozen runpy>", line 88, in _run_code\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto-pgo/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

bedevere-bot · 2025-03-28T12:41:30Z

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot s390x RHEL9 LTO 3.13 (tier-3) has failed when building commit 8f6a9aa.

What do you need to do:

Don't panic.
Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1577/builds/569) and take a look at the build logs.
Check if the failure is related to this commit (8f6a9aa) or if it is a false positive.
If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1577/builds/569

Failed tests:

test_repl

Failed subtests:

test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto/build/Lib/test/test_repl.py", line 304, in test_multiple_statements_fail_early
    self.assertNotIn("afterwards", output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 07:34:29) [GCC 11.5.0 20240719 (Red Hat 11.5.0-5)] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "<frozen runpy>", line 198, in _run_module_as_main\n  File "<frozen runpy>", line 88, in _run_code\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

…onGH-129488)

Use STATEMENT_FAILED and in InteractiveColoredConsole only

4d4ce3d

bswck requested review from pablogsal, lysnikolaou, ambv, 1st1, asvetlov, kumaraditya303 and willingc as code owners January 30, 2025 23:01

bedevere-app bot added the awaiting review label Jan 30, 2025

bedevere-app bot mentioned this pull request Jan 30, 2025

In the new REPL, multiline input execution should fail fast #128231

Closed

Simplify the test_multiple_statements_fail_early test

71c4a5f

bswck force-pushed the make-prompts-fail-early-in-repl branch from 1004941 to 71c4a5f Compare January 30, 2025 23:13

ZeroIntensity added the topic-repl Related to the interactive shell label Jan 31, 2025

Eclips4 reviewed Jan 31, 2025

View reviewed changes

Eclips4 approved these changes Jan 31, 2025

View reviewed changes

bedevere-app bot added awaiting merge and removed awaiting review labels Jan 31, 2025

Eclips4 added the needs backport to 3.13 bugs and security fixes label Jan 31, 2025

ZeroIntensity reviewed Feb 1, 2025

View reviewed changes

Lib/_pyrepl/console.py Show resolved Hide resolved

ZeroIntensity approved these changes Feb 12, 2025

View reviewed changes

encukou merged commit 7ed3dc6 into python:main Feb 24, 2025
66 checks passed

bedevere-app bot removed the awaiting merge label Feb 24, 2025

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Feb 24, 2025

pythongh-128231: Use runcode() return value for failing early (pyth…

2a59b10

…onGH-129488) (cherry picked from commit 7ed3dc6) Co-authored-by: Bartosz Sławecki <[email protected]>

bedevere-app bot removed the needs backport to 3.13 bugs and security fixes label Feb 24, 2025

hugovk mentioned this pull request Mar 28, 2025

[3.13] gh-128231: Use runcode() return value for failing early (GH-129488) #130513

Merged

hugovk added a commit to hugovk/cpython that referenced this pull request Mar 28, 2025

Revert "[3.13] pythongh-128231: Use runcode() return value for fail…

f32bd0a

…ing early (pythonGH-129488) (python#130513)" This reverts commit 8f6a9aa.

bswck mentioned this pull request Mar 28, 2025

gh-128231: Use runcode() return value for failing early (fix test) #131835

Closed

bswck mentioned this pull request Mar 28, 2025

gh-117174: Adapt test_multiple_statements_fail_early to new REPL behavior (follow-up gh-131065) #131836

Merged

bswck mentioned this pull request Mar 28, 2025

[3.13] gh-117174: Adapt test_multiple_statements_fail_early to new REPL behavior (follow-up gh-131065) (GH-131836) #131841

Merged

seehwan pushed a commit to seehwan/cpython that referenced this pull request Apr 16, 2025

pythongh-128231: Use runcode() return value for failing early (pyth…

adcbc6a

…onGH-129488)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

gh-128231: Use `runcode()` return value for failing early #129488

gh-128231: Use `runcode()` return value for failing early #129488

bswck commented Jan 30, 2025 •

edited

Loading

bswck commented Jan 30, 2025 •

edited

Loading

Eclips4 commented Jan 31, 2025

Eclips4 left a comment

bswck commented Feb 12, 2025

ZeroIntensity left a comment

bswck commented Feb 13, 2025 •

edited

Loading

encukou commented Feb 14, 2025

miss-islington-app bot commented Feb 24, 2025

bedevere-app bot commented Feb 24, 2025

bedevere-bot commented Mar 28, 2025

bedevere-bot commented Mar 28, 2025

ZeroIntensity commented Mar 28, 2025

bedevere-bot commented Mar 28, 2025

bedevere-bot commented Mar 28, 2025

bedevere-bot commented Mar 28, 2025

bedevere-bot commented Mar 28, 2025

bedevere-bot commented Mar 28, 2025

bedevere-bot commented Mar 28, 2025

bedevere-bot commented Mar 28, 2025

bedevere-bot commented Mar 28, 2025

bedevere-bot commented Mar 28, 2025

bedevere-bot commented Mar 28, 2025

hugovk commented Mar 28, 2025 •

edited

Loading

bedevere-bot commented Mar 28, 2025

bedevere-bot commented Mar 28, 2025

bedevere-bot commented Mar 28, 2025

bedevere-bot commented Mar 28, 2025

bedevere-bot commented Mar 28, 2025

gh-128231: Use runcode() return value for failing early #129488

gh-128231: Use runcode() return value for failing early #129488

Conversation

bswck commented Jan 30, 2025 • edited Loading

bswck commented Jan 30, 2025 • edited Loading

Eclips4 commented Jan 31, 2025

Eclips4 left a comment

Choose a reason for hiding this comment

bswck commented Feb 12, 2025

ZeroIntensity left a comment

Choose a reason for hiding this comment

bswck commented Feb 13, 2025 • edited Loading

encukou commented Feb 14, 2025

miss-islington-app bot commented Feb 24, 2025

bedevere-app bot commented Feb 24, 2025

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

ZeroIntensity commented Mar 28, 2025

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

hugovk commented Mar 28, 2025 • edited Loading

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

bedevere-bot commented Mar 28, 2025

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

gh-128231: Use `runcode()` return value for failing early #129488

gh-128231: Use `runcode()` return value for failing early #129488

bswck commented Jan 30, 2025 •

edited

Loading

bswck commented Jan 30, 2025 •

edited

Loading

bswck commented Feb 13, 2025 •

edited

Loading

hugovk commented Mar 28, 2025 •

edited

Loading