Transcript

1. pep8 vs PEP-8 Ian Lee @IanLee1521

2. The Setup…

3. Define Your Terms PEP-0008 aka PEP-8 
 (document) vs pep8


   (tool)

4. Define Your Terms PEP = Python Enhancement Proposal

5. Why am I? Leave everything better than you found it…

6. Who am I? Lawrence Livermore National Laboratory github.com/llnl — software.llnl.gov

   @LLNL_OpenSource

7. Who am I? • Maintainer: pep8 • Contributor: fastkml, pygeoif

   • Editor (?): benbalter.github.com

8. Quick Tangent… benbalter.github.com

9. Who am I? • Maintainer: pep8 • Contributor: fastkml, pygeoif

   • Editor (?): benbalter.github.com • One micro project: find-duplicates

10. Who am I?

11. Who am I? Scuba Diver

12. Who am I? Rock Climber

13. Who am I? Blues Dancer

14. Who am I? Love / hate relationship
 with technology…

15. Philmont April 2016

16. History *as I understand it

17. First Commit of PEP-8

18. PEPs are *not* static • 118 commits since 2001 •

    https://hg.python.org/peps/log/tip/pep-0008.txt?revcount=256

19. pep8 • Original Author: Johann C. Rocholl (@jcrocholl) • First

    commit: October 1, 2006 • PEP-8 had already changed 34 times

20. pep8 • Maintainer: Florent Xicluna (@florentx) • October 2009 -

    May 2014 + December 2014 • PEP-8 changed another 51 times

21. pep8 And now my turn…

22. pep8 • December 2014 - Present • PEP-8 changed another

    20 times • Total downloads > 17m

23. PyCQA . pycodestyle (pep8) astroid baron flake8 mccabe pydocstyle (pep257)

    redbaron flake8-docstrings mccabe-console-script pep8-naming

24. And then…

25. GitHub #466

26. pep8 -> pycodestyle

27. Hurdles…

28. ReadTheDocs

29. PyPI

30. Downstream

31. Progress to date…

32. pep8 == 1.7.1 Coming soon

33. pep8 == 1.7.1 Coming soon

34. pycodestyle == 2.0

35. #PyCon2016 Sprint Thursday Only

36. Government Open Space Tomorrow Morning / 10:00 / Room ==

    TBA

37. Thank You! @IanLee1521