cc. @berkerpeksag, @rhettinger, @serhiy-storchaka.

@rhettinger Would you mind reviewing the use of functools.lru_cache in this PR?

FYI @berkerpeksag, I've rebased onto master again, bco. #24801.

Rebased onto master to resolve conflicts. Also added a tiny optimisation: increase the default cache size from 100 to 128. I'm guessing it is way to late to get this into 3.10 now :)

@pablogsal, two questions:

1. There's some issues with the Windows tests. I've added a workaround in f1f023b, but I don't understand why this is needed. One possible reason could be that SQLite is holding on to TESTFN after the test is finished. I haven't devoted too much time to investigate this yet.
2. Is it ok to request Raymonds review here? functools is his domain.

2. Is it ok to request Raymonds review here? functools is his domain.

Unless you are changing the module itself, is not very relevant, but you are always free to ask for his advice :)

• There's some issues with the Windows tests. I've added a workaround in f1f023b, but I don't understand why this is needed. One possible reason could be that SQLite is holding on to TESTFN after the test is finished. I haven't devoted too much time to investigate this yet.

That seems like some genuine problem. Maybe @vstinner has seen this before?

When you are done with the fixes, could you test with the buildbots using the buildbot label?

I messed up the previous merge so I had to rebase and force push. Sorry 'bout the mess.

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

@erlend-aasland is this still a draft (I assume not)? :)

is this still a draft (I assume not)? :)

Nope, I was waiting for the CI, just to be sure :)

Great job @erlend-aasland! 🎉

Thanks, Pablo! 😃