This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xtreak
Recipients carlorosati, davin, josh.r, rhettinger, xiang.zhang, xtreak
Date 2018-08-28.11:00:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1535454013.96.0.56676864532.issue34410@psf.upfronthosting.co.za>
In-reply-to
Content
This might be redundant but I googled 'itertools tee thread safe' and came across a detailed SO answer from 2017 that explains the issue along with a similar example that causes segfault in the compiler but it was not reported here it seems. It also proposes a possible solution to fix the iterator but not tee itself. 

SO answer : https://stackoverflow.com/a/44638570/2610955

Similar open issue that could be a duplicate 

https://bugs.python.org/issue24482


Thanks
History
Date User Action Args
2018-08-28 11:00:14xtreaksetrecipients: + xtreak, rhettinger, josh.r, davin, xiang.zhang, carlorosati
2018-08-28 11:00:13xtreaksetmessageid: <1535454013.96.0.56676864532.issue34410@psf.upfronthosting.co.za>
2018-08-28 11:00:13xtreaklinkissue34410 messages
2018-08-28 11:00:13xtreakcreate