palantir/pyspark-style-guide
This is a guide to PySpark code style presenting common situations and the associated best practices based on the most frequent recurring topics across the PySpark repos we've encountered.
PythonMIT
Watchers
- abvthecity@palantir @fern-api
- akarnani
- akij
- bavardageNew York
- capattonUCLA
- clarkminorNYC / Palo Alto
- CRogers@palantir
- DavidMarraDC
- derekjobstPalantir Technologies
- elektron9@PromiseNetwork
- ellisjoePalantir
- ericlee996
- gillessed@palantir
- jamesevansPalantir
- jhcloos
- kkauff
- lostbeanPalantir
- lucasray
- lyubentUnited Kingdom
- mahmoudmSeattle, WA
- markgrex
- mckkLondon
- melonhead901@palantir
- mihirpandyaSan Jose, CA
- mlevinWashington, DC
- mudPalantir
- naves
- palantirtechPalantir Technologies
- pedrosaisseBrazil
- raiju
- rhysbrettbowenGoogle
- samsinensky
- saurabhshukla92
- trimitriInstitut für Physik der Humboldt-Universität zu Berlin
- whayler1Palantir
- xfalco