gh-109375: Fix bug where pdb registers an alias without an associated command #109376

buermarc · 2023-09-13T14:45:15Z

Issue: #109375

An unkown alias without a given command should not register a new alias.

Issue: pdb: calling registered alias without command raises KeyError #109375

ghost · 2023-09-13T14:45:18Z

All commit authors signed the Contributor License Agreement.

bedevere-app · 2023-09-13T14:45:21Z

Most changes to Python require a NEWS entry.

Please add it using the blurb_it web app or the blurb command-line tool.

An unkown alias without a given command should not register a new alias.

Lib/pdb.py

Lib/test/test_pdb.py

Co-authored-by: Tian Gao <[email protected]>

buermarc · 2023-09-14T11:59:17Z

I included the proposed changes. There was a failing test, because of an additional '.' (Unkown alias 'pi'.). I fixed it and squashed the two commits created by Github. Should i squash all commits or is it common to just squash when merging?

gaogaotiantian · 2023-09-14T18:44:47Z

You don't need to squash any commits on your feature branch. In fact, that is discouraged as it might make code review harder (to track the previous changes). The maintainers will squash all your commits when merging.

The code looks good to me. @iritkatriel

iritkatriel · 2023-09-14T19:04:32Z

@gaogaotiantian Is this a bugfix (should it be backported)?

Misc/NEWS.d/next/Library/2023-09-13-17-22-44.gh-issue-109375.ijJHZ9.rst

iritkatriel · 2023-09-14T19:13:34Z

@buermarc thanks for the fix. I see this is your first PR in this repo. Care to add your name to the Misc/ACKS file?

buermarc · 2023-09-14T19:25:49Z

Thanks for the reviewes

You don't need to squash any commits on your feature branch. In fact, that is discouraged as it might make code review harder (to track the previous changes). The maintainers will squash all your commits when merging.

That makes sense. Thanks for the info!

@buermarc thanks for the fix. I see this is your first PR in this repo. Care to add your name to the Misc/ACKS file?

I added my name, and tried to follow the "rough" alphabetical order :)

gaogaotiantian · 2023-09-14T21:12:01Z

@gaogaotiantian Is this a bugfix (should it be backported)?

I think we should backport it. It prevents pdb from raising an error in some situation - so not only improving user's experience, but actually protecting pdb's execution. Also it's not disruptive at all, very self-contained, easy to backport and very low risk.

gaogaotiantian · 2023-09-14T21:12:26Z

@buermarc thanks for the fix. I see this is your first PR in this repo. Care to add your name to the Misc/ACKS file?

Ha! I was not even in the list!

iritkatriel · 2023-09-14T21:28:48Z

@buermarc thanks for the fix. I see this is your first PR in this repo. Care to add your name to the Misc/ACKS file?

Ha! I was not even in the list!

Add yourself in your next PR.

miss-islington · 2023-09-14T21:31:33Z

Thanks @buermarc for the PR, and @iritkatriel for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12.
🐍🍒⛏🤖

…ciated command (pythonGH-109376) (cherry picked from commit 68a6f21) Co-authored-by: buermarc <[email protected]>

bedevere-app · 2023-09-14T21:31:43Z

GH-109429 is a backport of this pull request to the 3.12 branch.

…ciated command (pythonGH-109376) (cherry picked from commit 68a6f21) Co-authored-by: buermarc <[email protected]>

bedevere-app · 2023-09-14T21:31:47Z

GH-109430 is a backport of this pull request to the 3.11 branch.

bedevere-bot · 2023-09-14T21:37:56Z

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

Hi! The buildbot AMD64 RHEL7 3.x has failed when building commit 68a6f21.

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/all/#builders/15/builds/5675) and take a look at the build logs.
Check if the failure is related to this commit (68a6f21) 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/all/#builders/15/builds/5675

Failed tests:

test.test_asyncio.test_subprocess

Failed subtests:

test_subprocess_consistent_callbacks - test.test_asyncio.test_subprocess.SubprocessThreadedWatcherTests.test_subprocess_consistent_callbacks

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

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.x.cstratak-RHEL7-x86_64/build/Lib/test/test_asyncio/test_subprocess.py", line 788, in test_subprocess_consistent_callbacks
    self.loop.run_until_complete(main())
  File "/home/buildbot/buildarea/3.x.cstratak-RHEL7-x86_64/build/Lib/asyncio/base_events.py", line 664, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/home/buildbot/buildarea/3.x.cstratak-RHEL7-x86_64/build/Lib/test/test_asyncio/test_subprocess.py", line 780, in main
    self.assertEqual(events, [
AssertionError: Lists differ: ['process_exited', ('pipe_data_received', 1, b'stdout')] != [('pipe_data_received', 1, b'stdout'), ('p[95 chars]ted']

bedevere-bot · 2023-09-14T21:43:19Z

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

Hi! The buildbot s390x Debian 3.x has failed when building commit 68a6f21.

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/all/#builders/49/builds/6575) and take a look at the build logs.
Check if the failure is related to this commit (68a6f21) 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/all/#builders/49/builds/6575

Failed tests:

test.test_asyncio.test_unix_events

Failed subtests:

test_fork_signal_handling - test.test_asyncio.test_unix_events.TestFork.test_fork_signal_handling

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

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/dje/cpython-buildarea/3.x.edelsohn-debian-z/build/Lib/unittest/async_case.py", line 90, in _callTestMethod
    if self._callMaybeAsync(method) is not None:
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/dje/cpython-buildarea/3.x.edelsohn-debian-z/build/Lib/unittest/async_case.py", line 117, in _callMaybeAsync
    return self._asyncioTestContext.run(func, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/dje/cpython-buildarea/3.x.edelsohn-debian-z/build/Lib/test/support/hashlib_helper.py", line 49, in wrapper
    return func_or_class(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/dje/cpython-buildarea/3.x.edelsohn-debian-z/build/Lib/test/test_asyncio/test_unix_events.py", line 1937, in test_fork_signal_handling
    self.assertTrue(child_handled.is_set())
AssertionError: False is not true

bedevere-bot · 2023-09-14T22:07:54Z

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

Hi! The buildbot s390x RHEL7 3.x has failed when building commit 68a6f21.

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/all/#builders/179/builds/5482) and take a look at the build logs.
Check if the failure is related to this commit (68a6f21) 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/all/#builders/179/builds/5482

Failed tests:

test.test_asyncio.test_subprocess

Failed subtests:

test_subprocess_consistent_callbacks - test.test_asyncio.test_subprocess.SubprocessThreadedWatcherTests.test_subprocess_consistent_callbacks

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

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z/build/Lib/test/test_asyncio/test_subprocess.py", line 788, in test_subprocess_consistent_callbacks
    self.loop.run_until_complete(main())
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z/build/Lib/asyncio/base_events.py", line 664, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z/build/Lib/test/test_asyncio/test_subprocess.py", line 780, in main
    self.assertEqual(events, [
AssertionError: Lists differ: [('pi[29 chars]t'), 'pipe_connection_lost', ('pipe_data_recei[57 chars]ted'] != [('pi[29 chars]t'), ('pipe_data_received', 2, b'stderr'), 'pi[57 chars]ted']

bedevere-bot · 2023-09-14T22:07:59Z

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

Hi! The buildbot AMD64 RHEL8 LTO 3.x has failed when building commit 68a6f21.

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/all/#builders/64/builds/5063) and take a look at the build logs.
Check if the failure is related to this commit (68a6f21) 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/all/#builders/64/builds/5063

Failed tests:

test.test_asyncio.test_subprocess

Failed subtests:

test_subprocess_consistent_callbacks - test.test_asyncio.test_subprocess.SubprocessThreadedWatcherTests.test_subprocess_consistent_callbacks

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

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.x.cstratak-RHEL8-x86_64.lto/build/Lib/test/test_asyncio/test_subprocess.py", line 788, in test_subprocess_consistent_callbacks
    self.loop.run_until_complete(main())
  File "/home/buildbot/buildarea/3.x.cstratak-RHEL8-x86_64.lto/build/Lib/asyncio/base_events.py", line 664, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/home/buildbot/buildarea/3.x.cstratak-RHEL8-x86_64.lto/build/Lib/test/test_asyncio/test_subprocess.py", line 780, in main
    self.assertEqual(events, [
AssertionError: Lists differ: [('pi[69 chars]), 'process_exited', 'pipe_connection_lost', '[17 chars]ost'] != [('pi[69 chars]), 'pipe_connection_lost', 'pipe_connection_lo[17 chars]ted']

bedevere-bot · 2023-09-14T22:22:48Z

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

Hi! The buildbot AMD64 RHEL8 FIPS Only Blake2 Builtin Hash 3.x has failed when building commit 68a6f21.

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/all/#builders/469/builds/6003) and take a look at the build logs.
Check if the failure is related to this commit (68a6f21) 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/all/#builders/469/builds/6003

Failed tests:

test.test_asyncio.test_subprocess

Failed subtests:

test_subprocess_consistent_callbacks - test.test_asyncio.test_subprocess.SubprocessThreadedWatcherTests.test_subprocess_consistent_callbacks

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

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.x.cstratak-RHEL8-fips-x86_64.no-builtin-hashes-except-blake2/build/Lib/test/test_asyncio/test_subprocess.py", line 788, in test_subprocess_consistent_callbacks
    self.loop.run_until_complete(main())
  File "/home/buildbot/buildarea/3.x.cstratak-RHEL8-fips-x86_64.no-builtin-hashes-except-blake2/build/Lib/asyncio/base_events.py", line 664, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/home/buildbot/buildarea/3.x.cstratak-RHEL8-fips-x86_64.no-builtin-hashes-except-blake2/build/Lib/test/test_asyncio/test_subprocess.py", line 780, in main
    self.assertEqual(events, [
AssertionError: Lists differ: [('pi[29 chars]t'), 'pipe_connection_lost', ('pipe_data_recei[57 chars]ted'] != [('pi[29 chars]t'), ('pipe_data_received', 2, b'stderr'), 'pi[57 chars]ted']

bedevere-bot · 2023-09-14T22:26:46Z

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

Hi! The buildbot s390x RHEL7 LTO + PGO 3.x has failed when building commit 68a6f21.

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/all/#builders/244/builds/5445) and take a look at the build logs.
Check if the failure is related to this commit (68a6f21) 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/all/#builders/244/builds/5445

Failed tests:

test.test_multiprocessing_spawn.test_processes
test_tools

Failed subtests:

test_rapid_restart - test.test_multiprocessing_spawn.test_processes.WithProcessesTestManagerRestart.test_rapid_restart
test_freeze_simple_script - test.test_tools.test_freeze.TestFreeze.test_freeze_simple_script

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

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/Lib/test/_test_multiprocessing.py", line 3140, in test_rapid_restart
    manager.start()
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/Lib/multiprocessing/managers.py", line 569, in start
    self._address = reader.recv()
                    ^^^^^^^^^^^^^
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/Lib/multiprocessing/connection.py", line 251, in recv
    buf = self._recv_bytes()
          ^^^^^^^^^^^^^^^^^^
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/Lib/multiprocessing/connection.py", line 431, in _recv_bytes
    buf = self._recv(4)
          ^^^^^^^^^^^^^
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/Lib/multiprocessing/connection.py", line 400, in _recv
    raise EOFError
EOFError


Traceback (most recent call last):
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/Lib/multiprocessing/process.py", line 314, in _bootstrap
    self.run()
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/Lib/multiprocessing/process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/Lib/multiprocessing/managers.py", line 594, in _run_server
    server = cls._Server(registry, address, authkey, serializer)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/Lib/multiprocessing/managers.py", line 159, in __init__
    self.listener = Listener(address=address, backlog=16)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/Lib/multiprocessing/connection.py", line 465, in __init__
    self._listener = SocketListener(address, family, backlog)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/Lib/multiprocessing/connection.py", line 608, in __init__
    self._socket.bind(address)
OSError: [Errno 98] Address already in use


Traceback (most recent call last):
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/Lib/test/test_tools/test_freeze.py", line 28, in test_freeze_simple_script
    outdir, scriptfile, python = helper.prepare(script, outdir)
                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/Tools/freeze/test/freeze.py", line 146, in prepare
    copy_source_tree(srcdir, SRCDIR)
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/Tools/freeze/test/freeze.py", line 95, in copy_source_tree
    shutil.copytree(oldroot, newroot, ignore=ignore_non_src)
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/Lib/shutil.py", line 588, in copytree
    return _copytree(entries=entries, src=src, dst=dst, symlinks=symlinks,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/Lib/shutil.py", line 542, in _copytree
    raise Error(errors)
shutil.Error: [('/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/build/test_python_56668æ', '/tmp/test_python_9hv_hwrk/tmp7jgq9ehf/cpython/build/test_python_56668æ', "[Errno 2] No such file or directory: '/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto-pgo/build/build/test_python_56668æ'")]

bedevere-bot · 2023-09-14T22:54:59Z

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

Hi! The buildbot AMD64 Fedora Stable LTO + PGO 3.x has failed when building commit 68a6f21.

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/all/#builders/29/builds/4743) and take a look at the build logs.
Check if the failure is related to this commit (68a6f21) 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/all/#builders/29/builds/4743

Failed tests:

test.test_asyncio.test_unix_events
test.test_asyncio.test_subprocess

Failed subtests:

test_subprocess_consistent_callbacks - test.test_asyncio.test_subprocess.SubprocessPidfdWatcherTests.test_subprocess_consistent_callbacks
test_fork_signal_handling - test.test_asyncio.test_unix_events.TestFork.test_fork_signal_handling

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

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-x86_64.lto-pgo/build/Lib/test/test_asyncio/test_subprocess.py", line 788, in test_subprocess_consistent_callbacks
    self.loop.run_until_complete(main())
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-x86_64.lto-pgo/build/Lib/asyncio/base_events.py", line 664, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-x86_64.lto-pgo/build/Lib/test/test_asyncio/test_subprocess.py", line 780, in main
    self.assertEqual(events, [
AssertionError: Lists differ: [('pi[69 chars]), 'process_exited', 'pipe_connection_lost', '[17 chars]ost'] != [('pi[69 chars]), 'pipe_connection_lost', 'pipe_connection_lo[17 chars]ted']


Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-x86_64.lto-pgo/build/Lib/unittest/async_case.py", line 90, in _callTestMethod
    if self._callMaybeAsync(method) is not None:
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-x86_64.lto-pgo/build/Lib/unittest/async_case.py", line 117, in _callMaybeAsync
    return self._asyncioTestContext.run(func, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-x86_64.lto-pgo/build/Lib/test/support/hashlib_helper.py", line 49, in wrapper
    return func_or_class(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-x86_64.lto-pgo/build/Lib/test/test_asyncio/test_unix_events.py", line 1937, in test_fork_signal_handling
    self.assertTrue(child_handled.is_set())
AssertionError: False is not true

…ociated command (GH-109376) (#109430) gh-109375: Fix bug where pdb registers an alias without an associated command (GH-109376) (cherry picked from commit 68a6f21) Co-authored-by: buermarc <[email protected]>

…ociated command (GH-109376) (#109429) gh-109375: Fix bug where pdb registers an alias without an associated command (GH-109376) (cherry picked from commit 68a6f21) Co-authored-by: buermarc <[email protected]>

bedevere-app bot added the awaiting review label Sep 13, 2023

bedevere-app bot mentioned this pull request Sep 13, 2023

pdb: calling registered alias without command raises KeyError #109375

Closed

buermarc force-pushed the fix-pdb-alias-command branch from 88b9e45 to 37a1969 Compare September 13, 2023 14:55

AlexWaygood requested a review from gaogaotiantian September 13, 2023 15:07

pythongh-109375: Fix pdb alias command

1393e36

An unkown alias without a given command should not register a new alias.

buermarc force-pushed the fix-pdb-alias-command branch from 37a1969 to 1393e36 Compare September 13, 2023 15:23

gaogaotiantian requested changes Sep 13, 2023

View reviewed changes

Lib/pdb.py Outdated Show resolved Hide resolved

Lib/test/test_pdb.py Outdated Show resolved Hide resolved

bedevere-app bot added awaiting core review and removed awaiting review labels Sep 13, 2023

Update Lib/pdb.py, Lib/test/test_pdb.py

0fae8eb

Co-authored-by: Tian Gao <[email protected]>

buermarc force-pushed the fix-pdb-alias-command branch from d93460f to 0fae8eb Compare September 14, 2023 09:15

gaogaotiantian approved these changes Sep 14, 2023

View reviewed changes

gaogaotiantian requested a review from iritkatriel September 14, 2023 18:45

iritkatriel approved these changes Sep 14, 2023

View reviewed changes

iritkatriel added stdlib Python modules in the Lib dir and removed awaiting core review labels Sep 14, 2023

iritkatriel reviewed Sep 14, 2023

View reviewed changes

Misc/NEWS.d/next/Library/2023-09-13-17-22-44.gh-issue-109375.ijJHZ9.rst Outdated Show resolved Hide resolved

iritkatriel added 2 commits September 14, 2023 20:12

tweak news

94ff15c

Merge branch 'main' into fix-pdb-alias-command

6570066

Add name to Misc/ACKS

45adcb4

iritkatriel changed the title ~~gh-109375: Fix pdb alias command~~ gh-109375: Fix bug where pdb's 'alias' registers an alias without an associated command Sep 14, 2023

iritkatriel added type-bug An unexpected behavior, bug, or error needs backport to 3.11 only security fixes needs backport to 3.12 only security fixes labels Sep 14, 2023

iritkatriel changed the title ~~gh-109375: Fix bug where pdb's 'alias' registers an alias without an associated command~~ gh-109375: Fix bug where pdb registers an alias without an associated command Sep 14, 2023

iritkatriel merged commit 68a6f21 into python:main Sep 14, 2023

bedevere-app bot removed the needs backport to 3.12 only security fixes label Sep 14, 2023

bedevere-app bot removed the needs backport to 3.11 only security fixes label Sep 14, 2023

buermarc deleted the fix-pdb-alias-command branch September 30, 2023 13:53

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

gh-109375: Fix bug where pdb registers an alias without an associated command #109376

gh-109375: Fix bug where pdb registers an alias without an associated command #109376

buermarc commented Sep 13, 2023 •

edited by bedevere-app bot

Loading

ghost commented Sep 13, 2023 •

edited by ghost

Loading

bedevere-app bot commented Sep 13, 2023

buermarc commented Sep 14, 2023

gaogaotiantian commented Sep 14, 2023

iritkatriel commented Sep 14, 2023

iritkatriel commented Sep 14, 2023 •

edited

Loading

buermarc commented Sep 14, 2023 •

edited by iritkatriel

Loading

gaogaotiantian commented Sep 14, 2023

gaogaotiantian commented Sep 14, 2023 •

edited by iritkatriel

Loading

iritkatriel commented Sep 14, 2023 •

edited

Loading

miss-islington commented Sep 14, 2023

bedevere-app bot commented Sep 14, 2023

bedevere-app bot commented Sep 14, 2023

bedevere-bot commented Sep 14, 2023

bedevere-bot commented Sep 14, 2023

bedevere-bot commented Sep 14, 2023

bedevere-bot commented Sep 14, 2023

bedevere-bot commented Sep 14, 2023

bedevere-bot commented Sep 14, 2023

bedevere-bot commented Sep 14, 2023

gh-109375: Fix bug where pdb registers an alias without an associated command #109376

gh-109375: Fix bug where pdb registers an alias without an associated command #109376

Conversation

buermarc commented Sep 13, 2023 • edited by bedevere-app bot Loading

ghost commented Sep 13, 2023 • edited by ghost Loading

bedevere-app bot commented Sep 13, 2023

buermarc commented Sep 14, 2023

gaogaotiantian commented Sep 14, 2023

iritkatriel commented Sep 14, 2023

iritkatriel commented Sep 14, 2023 • edited Loading

buermarc commented Sep 14, 2023 • edited by iritkatriel Loading

gaogaotiantian commented Sep 14, 2023

gaogaotiantian commented Sep 14, 2023 • edited by iritkatriel Loading

iritkatriel commented Sep 14, 2023 • edited Loading

miss-islington commented Sep 14, 2023

bedevere-app bot commented Sep 14, 2023

bedevere-app bot commented Sep 14, 2023

bedevere-bot commented Sep 14, 2023

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

bedevere-bot commented Sep 14, 2023

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

bedevere-bot commented Sep 14, 2023

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

bedevere-bot commented Sep 14, 2023

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

bedevere-bot commented Sep 14, 2023

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

bedevere-bot commented Sep 14, 2023

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

bedevere-bot commented Sep 14, 2023

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

buermarc commented Sep 13, 2023 •

edited by bedevere-app bot

Loading

ghost commented Sep 13, 2023 •

edited by ghost

Loading

iritkatriel commented Sep 14, 2023 •

edited

Loading

buermarc commented Sep 14, 2023 •

edited by iritkatriel

Loading

gaogaotiantian commented Sep 14, 2023 •

edited by iritkatriel

Loading

iritkatriel commented Sep 14, 2023 •

edited

Loading