Pieter Eendebak

> > The _deepcopy_fallback is only used for objects not handled by the C deepcopy method (and vice versa). therefore we cannot test both the fallback and C on the...

I addressed some of the review comments. @serhiy-storchaka Could you indicate which issues with the `copy` module there are, and whether there already is a timeline on addressing them?

@tiran Thanks for reviewing, with your feedback the PR is in much better shape now. I addressed the comments (except for the one about `_Py_hashtable_t` which I still have to...

Output of the pyperformance [deepcopy benchmark](https://github.com/python/pyperformance/tree/main/pyperformance/data-files/benchmarks/bm_deepcopy): ``` deepcopy: Mean +- std dev: [main] 414 us +- 4 us -> [pr] 128 us +- 2 us: 3.23x faster deepcopy_reduce: Mean +-...

I have made the requested changes; please review again

@tiran I updated to merge with #94474.

> Thanks! I'll come back to your PR once 3.11 has reached RC phase. @tiran Would you have time to review the PR?

@serhiy-storchaka @tiran The behaviour of the new deepcopy implementation is different from the current one for the following case: ``` import copy class A: # class with evil deepcopy def...

The slow execution of `git_pieces_from_vcs` is mainly due to execution of a `git describe` command. This can be slow if there has been a large number of commits since the...

@axil Personally, I do not have a strong opinion on whether to use a dot, asterisk or no multiplication symbol (in either latex or str). But I am a bit...