summaryrefslogtreecommitdiffstats
path: root/Lib/test/_test_multiprocessing.py
diff options
context:
space:
mode:
authorBarney Gale <barney.gale@gmail.com>2024-04-05 18:51:54 (GMT)
committerGitHub <noreply@github.com>2024-04-05 18:51:54 (GMT)
commit6150bb2412eb5ca3b330ccb9f0636949c7526a7f (patch)
tree627dc7282bd5eb5ab2998c5d652b46dbdd77ecc6 /Lib/test/_test_multiprocessing.py
parent4d4a6f1b6aea6dae131ac116f1735a38c3e32cd1 (diff)
downloadcpython-6150bb2412eb5ca3b330ccb9f0636949c7526a7f.zip
cpython-6150bb2412eb5ca3b330ccb9f0636949c7526a7f.tar.gz
cpython-6150bb2412eb5ca3b330ccb9f0636949c7526a7f.tar.bz2
GH-77609: Add recurse_symlinks argument to `pathlib.Path.glob()` (#117311)
Replace tri-state `follow_symlinks` with boolean `recurse_symlinks` argument. The new argument controls whether symlinks are followed when expanding recursive `**` wildcards. The possible argument values correspond as follows: follow_symlinks recurse_symlinks =============== ================ False N/A None False True True We therefore drop support for not following symlinks when expanding non-recursive pattern parts; it wasn't requested in the original issue, and it's a feature not found in any shells. This makes the API a easier to grok by eliminating `None` as an option. No news blurb as `follow_symlinks` was new in 3.13.
Diffstat (limited to 'Lib/test/_test_multiprocessing.py')
0 files changed, 0 insertions, 0 deletions