Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Lint-Review by Adrian Moisey
Search
Pycon ZA
October 05, 2017
Programming
110
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Lint-Review by Adrian Moisey
A Lightning Talk at PyConZA 2017
Pycon ZA
October 05, 2017
More Decks by Pycon ZA
See All by Pycon ZA
Trio: Structured Concurrency for Python by Jeremy Thurgood
pyconza
0
270
Preparing for the great snakes migration by Heather Williams
pyconza
0
110
Satellite Data and Super-Resolution to enhance a Slope Soaring Simulator by Schalk Heunis
pyconza
0
190
"Should we just go home on the third Friday afternoon?" by Kim van Wyk
pyconza
0
140
"Dolosse: Distributed Physics Data Acquisition System" by Bertram Losper & Sehlabaka Qhobosheane
pyconza
0
190
Modern JavaScript for Python Developers by Cory Zue
pyconza
0
350
Making Art with Python by Kirk Kaiser
pyconza
0
250
"Posits: A proposed new floating point number format for ML" by Kevin Colville
pyconza
0
160
"Building a label printer using Python, Arduino, duct tape and paperclips" by Johan Beyers
pyconza
0
330
Other Decks in Programming
See All in Programming
5分で問診!Composer セキュリティ健康診断
codmoninc
0
590
Hatena Engineer Seminar #37「言語モデルの活用に関する研究」
slashnephy
0
540
壊れたパーサから始める関数型設計と構成的なパーサ #fp_matsuri
raiga0310
2
400
【SRE NEXT 2026 Lunch Session】一人目専任SREの立ち上げを加速する ― AIと進めたオンボーディングで2分を0.04秒にした話
pkshadeck
PRO
0
3k
GitHubCopilotCLIのスラッシュコマンドを自作してみる
htkym
0
100
『コードを書く以外の』エンジニアリング〜課金基盤移行プロジェクト推進のためのTips4選
yuriko1211
0
540
ルールを書いて終わらせないハーネスエンジニアリング
yug1224
4
1.7k
PHP Application における Kubernetes 内 gRPC 通信
ganchiku
0
530
作るコストが小さくなった時代 幸せに働くために改めて考えたいこと 〜エンジニアとして価値を出し続けるために注視している二分野〜
yuppeeng
0
120
【やさしく解説 設計編・中級 #1】一つの車に、運転手は一人 ~ある倉庫システムの事例から~
panda728
PRO
0
190
Welcome to the "Parametricity" 🏙️ − Generic だけど Specific な世界 −
guvalif
PRO
1
180
ITヒヤリハットを整理してみた ~ライフサイクルと原因から考える再発防止策~
koukimiura
1
110
Featured
See All Featured
Dealing with People You Can't Stand - Big Design 2015
cassininazir
367
27k
Documentation Writing (for coders)
carmenintech
77
5.4k
New Earth Scene 8
popppiees
3
2.4k
Raft: Consensus for Rubyists
vanstee
141
7.6k
The SEO identity crisis: Don't let AI make you average
varn
0
520
Game over? The fight for quality and originality in the time of robots
wayneb77
1
230
Unlocking the hidden potential of vector embeddings in international SEO
frankvandijk
0
880
Applied NLP in the Age of Generative AI
inesmontani
PRO
4
2.4k
SEO Brein meetup: CTRL+C is not how to scale international SEO
lindahogenes
1
2.8k
The Cult of Friendly URLs
andyhume
79
7k
Building Adaptive Systems
keathley
44
3.1k
Visualization
eitanlees
152
17k
Transcript
Lint Review https://github.com/markstory/lint-review Adrian Moisey adrian on zatech slack adrianmoisey
on GitLab and GitHub
Why style your code? • Consistency • Easier to read
• Follow community/official standards (PEP-8, Rubocop, PHPCS, JCSC) • Familiarity with foreign code bases
But I just don’t care about style... • Some linters
catch syntax errors • Flake8 catches some code breaking syntax errors
Why Lint Review? • It runs against a GitHub Pull
Request ◦ It only cares about the code that you actually changed • Helps to style an unstyled codebase • Easy to add more linters (it’s written in Python + Flask)
Demo time… Just a screenshot instead...
None
None
Features I’d like to see, if you want to help
out... • Python 3 • Mypy • GitLab