[issue19441] itertools.tee improve documentation

Raymond Hettinger added the comment: This is out of date. The docs currently have: ''' Once :func:`tee` has made a split, the original *iterable* should not be used anywhere else; otherwise, the *iterable* could get advanced without the tee objects being informed. ''' -- resolution

[issue19441] itertools.tee improve documentation

Alan Cristhian added the comment: Ok, I agree. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue19441] itertools.tee improve documentation

Raymond Hettinger added the comment: I don't want to recommend overwriting the variable name but will add a note for the rest: "Copied iterators depend the original iterator. If the original advances, then so do the copies. After teeing the iterators, the usual practice is to stop working wit

[issue19441] itertools.tee improve documentation

Changes by Raymond Hettinger : -- assignee: docs@python -> rhettinger nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list ma

[issue19441] itertools.tee improve documentation

New submission from Alan Cristhian: I had some problems using itertools.tee function. Fortunately I found the following advice on the PEP-323: "Currently, the copied iterators remaintied to the original iterator. If the original advances, then so do all of the copies. Good practice is to overw