[issue14350] Strange Exception from copying an iterator

Changes by Serhiy Storchaka : -- dependencies: -Restrict default pickleability resolution: -> duplicate stage: needs patch -> resolved status: open -> closed superseder: -> Restrict default pickleability ___ Python tracker

[issue14350] Strange Exception from copying an iterator

Serhiy Storchaka added the comment: Actually the tp_new field of list iterator class is NULL. Unpickler raises other error in such case (see issue24900 for example). UnpicklingError: NEWOBJ class argument has NULL tp_new Backported to 2.7 the part of the patch for issue22995 fixes this

[issue14350] Strange Exception from copying an iterator

Jakob Bowyer jkb...@gmail.com added the comment: Before anyone else rushes of to do this, can I? I really want to break into python-dev and this might be my chance. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14350

[issue14350] Strange Exception from copying an iterator

R. David Murray rdmur...@bitdance.com added the comment: Please, give it a try. But also be prepared for it being harder than it looks; the problem is that there may be very limited knowledge available where the error is generated. (I don't know; I haven't looked at the code and am not

[issue14350] Strange Exception from copying an iterator

Terry J. Reedy tjre...@udel.edu added the comment: Title corrected. Non-iterator iterables are usually easy to copy. I think this is in the category of don't do that ;-) I believe the idea of making iterators copyable has been rejected on one of the lists because it is probably not possible in