Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA).

Recognized GitHub username

We couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames:

@mustafaquraish

This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

You can check yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

The docs should definitely be updated for this. I also see a test for this specific function does not exist yet, this seems like a good chance to add one?

The docs should definitely be updated for this. I also see a test for this specific function does not exist yet, this seems like a good chance to add one?

@DimitrisJim , thanks for the feedback. I'm still new to the project, and would like to help out with this, so can you point me as to how to go about this? From what I see the documentation for this function looks like it has been auto-generated from the docstrings, and the tests (which I can run with ./python.exe -m test test_difflib) are just using the tests from the docstrings for each function. I have updated those to reflect the new argument as well as added a test for the key feature.

Is there a more official place to put these? I'm not 100% confident on the internal algorithms for difflib, so I'm not sure I would be the best one to be writing a full test suite for it (I wouldn't know how to properly check the edge cases with the cutoff parameter for instance). My development process for this PR was just finding every occurrence of the function inside the source with the updated version.

Of course! Docs are relatively straight-forward to add, from what I remember, they aren't built automatically.

The Devguide section on this explains most of what you'll need to know. It basically boils down to opening the corresponding file for difflib in the Docs/lib folder (difflib.rst) and adding the docs you've added in the function docstring (looking at difflib.rst it does contain exactly the same text as in the function docstring, so I see how it looks as if they've been auto-generated).

For tests, usually you'd add a unit test to Lib/test/test_difflib.py but I'm thinking a reason might exist that this function hasn't been explicitly tested yet (maybe doctests suffice). The reviewer, who maintains the module, will probably have more to say on this.

This PR is stale because it has been open for 30 days with no activity.

@tim-one any chance you could review this anytime soon? It's a pretty minor change.

Please add to Docs as get_close_matches(word, possibilities, n=3, cutoff=0.6) needs changing. Also, please add version changed: 3.12 (is earliest).