[issue28250] typing.NamedTuple instances are not picklable Two

urday, September 24, 2016 1:43 AM Subject: [issue28250] typing.NamedTuple instances are not picklable Two Mark Dickinson added the comment: I don't think this has anything to do with namedtuple; it's true whenever you create a class in an inner scope (rather than at module level). Thi

[issue28250] typing.NamedTuple instances are not picklable Two

Mark Dickinson added the comment: I don't think this has anything to do with namedtuple; it's true whenever you create a class in an inner scope (rather than at module level). This is by design, and these restrictions are documented: https://docs.python.org/3.6/library/pickle.html#what-can-be-

[issue28250] typing.NamedTuple instances are not picklable Two

Changes by Ivan Levkivskyi : -- nosy: +levkivskyi ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue28250] typing.NamedTuple instances are not picklable Two

New submission from Kurt Dally: Creating a namedtuple and an instance of the namedtuple in a function then returning the instance to the global namespace made the instance unpickleable, as in Issue25665. -- components: Library (Lib) messages: 277236 nosy: Kurt priority: normal severity