Clarify use of the lock. Add message to the ValueError.

python · rhettinger · Apr 22, 2026 · Apr 23, 2026 · Apr 23, 2026 · Apr 23, 2026
commit adcb718b3341e7dbaad9d1b620ea6f85b13d6320
diff --git a/Doc/library/threading.rst b/Doc/library/threading.rst
@@ -1464,10 +1464,9 @@ of the derived iterators.
    :meth:`~iterator.__next__` using a lock.
 
    This makes it possible to share a single iterator, including a generator
-   iterator, between multiple threads. Calls are handled one at a time in
-   arrival order determined by lock acquisition. No values are duplicated or
-   skipped by the wrapper itself. Each item produced by the underlying iterator
-   is given to exactly one caller.
+   iterator, between multiple threads. A lock assures that calls are handled
+   one at a time. No values are duplicated or skipped by the wrapper itself.
+   Each item from the underlying iterator is given to exactly one caller.
 
    This wrapper does not copy or buffer values. Threads that call
    :func:`next` while another thread is already advancing the iterator will

diff --git a/Lib/threading.py b/Lib/threading.py
@@ -910,7 +910,7 @@ def concurrent_tee(iterable, n=2):
     """
 
     if n < 0:
-        raise ValueError
+        raise ValueError("n must be positive integer")
     if n == 0:
         return ()
     iterator = _concurrent_tee(iterable)