Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1623#issuecomment-50954307
Calling `_hack_namedtuple()` should set up pickling for any `namedtuple`
subclasses defined up to that point. It looks like we re-assign to
`collections.namedtuple`, but by then it's already too late since the user
might have a reference to the original, non-wrapped `namedtuple` class. Is
there any easy way to patch the `namedtuple` object itself so that it injects
the hack? I think that would solve the problem, since any new `namedtuple`
classes would automatically receive the hack and any old ones would be handled
by our search through `__main__`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
