gh-101100: Fix dangling refs in bdb.rst#114983
Conversation
Co-authored-by: AN Long <aisk@users.noreply.github.com>
serhiy-storchaka
left a comment
There was a problem hiding this comment.
LGTM.
Sorry, something went wrong.
|
@smontanaro Please could you update this PR to remove
|
Sorry, something went wrong.
|
@hugovk Should be all set. If my aim at the start of one of these mini-projects is to get rid of all warnings from a file, should my initial PR remove it from |
Sorry, something went wrong.
|
Yes please, we can consider each PR to be atomic so both (clean file, remove from .nitignore) are needed for the CI to pass, and the CI must pass for us to be able to merge. |
Sorry, something went wrong.
|
Thanks @smontanaro for the PR, and @hugovk for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12. |
Sorry, something went wrong.
|
Sorry, @smontanaro and @hugovk, I could not cleanly backport this to |
Sorry, something went wrong.
(cherry picked from commit 1b89591) Co-authored-by: Skip Montanaro <skip.montanaro@gmail.com> Co-authored-by: AN Long <aisk@users.noreply.github.com>
Co-authored-by: AN Long <aisk@users.noreply.github.com> (cherry picked from commit 1b89591)
|
Cherries have been picked. I think I finally created the pull request against the correct branch (3.12). Given the standardized naming of the backport branch, it does seem peculiar that GitHub can't default to the relevant branch though... |
Sorry, something went wrong.
Looks great! There was just one thing missing: a backport PR to the 3.12 branch has to have a PR title starting with |
Sorry, something went wrong.
Co-authored-by: AN Long <aisk@users.noreply.github.com>
This should be fairly straightforward. I did one thing that isn't maybe strictly kosher. The
Bdb.quittingattribute isn't directly documented, but is mentioned in the description ofBdb.set_quit(). I linked those occurrences to the description ofset_quit.📚 Documentation preview 📚: https://cpython-previews--114983.org.readthedocs.build/