Matthew Powers

@alfonsorr - I like the idea of backporting functionality to earlier versions of Spark. Doesn't seem like this'll increase the maintenance burden of the project too much. @nvander1 @yaooqinn -...

@yelled1 - I removed the hard dependency on PySpark, hopefully this will solve the issue. The hard PySpark dependency [caused an issue on another project as well](https://github.com/MrPowers/chispa/issues/6). I just [published...

Yea, perhaps vendoring Jellyfish is the best path forward to avoid the transitive dependency issue. Python packaging is difficult and even harder when Spark is added to the mix.

@evangeliazve - thanks for reporting this. I'm not sure how to fix the issue. Can you please send me your exact code and the full error stack trace, so I...

@slavyolov - thanks for opening the issue. I'm open to the suggestion, but not entirely sure I understand how the output will be different. Can you open a PR and...

@fraserpal - looks good, thanks for opening this. Can you please add a couple tests?

@fraserpal - thanks for the suggestion, sounds like a good idea. Would you like to send a PR?

@mitches-got-glitches - thanks for following up and sorry for the delay. Here are my main objectives with this PR: * Get your new functionality included in the lib cause it's...

Looks like [Spark 2.4.5 technically supports Python 3.4+](https://spark.apache.org/docs/2.4.5/) and I'd still like to support the Spark 2 users for a bit longer. That said, seems reasonable to set the Python...

@mitches-got-glitches - great, glad we're still supporting PySpark 2.4 😉 Updated [the required Python version](https://github.com/MrPowers/chispa/commit/bee145406b8bb39df0267e77ccd9ea98027d1c12). So yes, the `typing` module question is resolved. We're requiring Python 3.5+ now, so using...