Github user superbobry commented on the issue:
https://github.com/apache/spark/pull/21180
> Yea the next will likely be 3.0.0 and actually many fixes are being
targeted to 3.0.0 (even one of mine).
Awesome, I'm OK to wait until 3.0.0 then. Is there a release date already?
> I thought this only affects globally defined named tuple, no?
It does, but it is very likely that 99% of the namedtuples used in Python
programs are defined globally. The ones defined in the PySpark shell would work
as well, assuming they are proper namedtuples and not classes inheriting
namedtuples.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
