Graham Cummins <grahamiancumm...@gmail.com> added the comment: As far as I can tell, this is a version of the scope-dependent un-pickling issue mentioned in the documentation. I'm still rather confused, since in the original occurrence of the issue happens despite the fact that subprocesses should be able to import all relevant modules (unless they have a very odd environment), and the original class is pickleable. Still, until I can clearly distinguish my difficulty from the know issues presented in the programming guidelines, I see no reason to have it listed as a bug.
---------- resolution: -> invalid status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12227> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
