| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
…ctory changed This commit only adds tests and a news entry. The actual bug was fixed in the earlier commit.
|
Now that #23338 is merged this can also be merged. #23338 fixed both bpo-42383 and bpo-42384 with a one-line change, but the test for bpo-42383 was split into a separate PR as recommended in #23338 (comment) |
Sorry, something went wrong.
|
Something's missing -- this just adds a test but doen't change anything in pdb.py. |
Sorry, something went wrong.
There was a problem hiding this comment.
Oh wait that's because the other PR fixed both issues.
Next time I think you should just do everything in one PR. :-)
Sorry, something went wrong.
|
@gvanrossum: Please replace # with GH- in the commit message next time. Thanks! |
Sorry, something went wrong.
|
@hexagonrecursion Is it worth backporting this too? |
Sorry, something went wrong.
I already did. |
Sorry, something went wrong.
…ctory changed (python#23412) This commit only adds tests and a news entry. The actual bug was fixed in the earlier commit.
| Back | FazBrowse Home | New Git URL |
#23338 should be merged first because it contains the actual fix since both https://bugs.python.org/issue42383 and https://bugs.python.org/issue42384 can be fixed by adding one line.
Following this instructions
#23338 (comment)
I opened a separate PR for bpo-42383
https://bugs.python.org/issue42383