#PEP8
PEP8 spaces*
May 4, 2026 at 12:48 PM
I'm watching a talk about pep8, instead of being productive, and the presenter keeps saying the biggest issue with pep8 is that programmers focus on it too much instead of actually being productive. I'm built different tho.
March 15, 2024 at 10:18 PM
pep8, basically
February 17, 2024 at 12:55 AM
they should do a PEP8 but 𝒻ℴ𝓇 ℊ𝒾𝓇𝓁𝓈
May 12, 2026 at 1:16 PM
As a coding dinosaur (mother tongue fortran) my "suck-it-and-see" approach to python isn't as strong as it should be. @joezuntz.bsky.social spat his tea out when reviewing a recent commit, kindly pointing me to PEP8 & "black". It's pure magic! Now my code is so pretty 💃
ℹ️: pypi.org/project/black/
September 3, 2025 at 6:12 AM
Interviewer: Can you explain this gap in your resume?

software dev: PEP8
Interviewer: Can you explain this gap in your resume?

Linguist: That’s the undocumented stage. Reconstructable only through comparative method.
Interviewer: Can you explain this gap in your resume?

Indexer: Resume, gap in. See under Gap in resume
May 12, 2025 at 5:59 PM
PEP8 my despised
August 6, 2025 at 10:58 PM
PEP8 is wrong and using double-quotes for your docstrings is objectively incorrect :v
April 11, 2025 at 2:49 AM
世界的に見ても開発標準に基づいたシステムの方が少ないので、それらを学習した生成AIが吐き出してくるプログラムの品質には疑問が残ります。
ChatGPT先生なんかは、PythonのコードをPEP8準拠で答えてくれますが、PEP8は最小限のコーディングルールなので、それを守っているから品質が担保できるわけではありません。もっとも、それすら守らなければ、品質も何もあったもんじゃないのですが😓
March 12, 2025 at 3:52 AM
prompted by a discussion about naming things elsewhere
February 22, 2026 at 7:55 PM
PEP8を厳守しろ!!!
August 25, 2026 at 10:07 AM
clarification: all the code is documented. i obey pep8.
January 21, 2024 at 12:35 AM
Do you care about PEP8 rules when you implement Python code?

#softwaredevelopment #python #followtherules #notinchristmas
December 19, 2024 at 7:32 AM
LOL you are the reason PEP8 exists!
December 19, 2024 at 3:36 AM
my boss threw together some bullshit python using claude and i took one fucking look at it and went "that aint pep8."

had to refactor 300 lines of cunt.
September 24, 2026 at 3:42 PM
I was looking into Ruff, as it has some nice formatting stuff built in, but I gotta say the weird forcing of some PEP8 things vs not others is kinda annoying.
March 2, 2025 at 7:36 PM
I am the bone of my prompt
Steel is my body and context is my blood
I have refactored over a thousand scripts
Unknown to PEP8,
Nor known to PyPI.
Have withstood errors to deprecate many modules
Yet, those hands will never write a single `def`
So as I pray, Unlimited Code Purge.
l4.pm luna @l4.pm · Mar 15
the purpose of agentic coding is to empower us to decrease the amount of python in the world

(ive been writing py for many years. im allowed to make this post)
March 15, 2026 at 9:54 PM
B, because A isn't pep8
November 8, 2023 at 12:25 AM
La pep8 en NSI ? Vous avez des extra terrestres ou c’est comment ?
August 3, 2026 at 10:26 AM
It is abundantly clear nobody here has heard about PEP8 compliance or Ruff cause everyone uses different cases across schemas and tables and its driving me goddamn insane
July 14, 2026 at 3:48 PM
I guess it would be fine if pep8 didn't like, suck so badly, but I honestly find it much much harder to read code that is pep8 formatted, so things like black and autopep8 just *dont* work for me.
June 5, 2025 at 9:25 PM
I've found this part useful to help programmers and reviewers to align their coding style accordingly to PEP8, better readability, and to use underscores instead of camelCase

Does your company do something similar to this?
#programmer
July 14, 2025 at 11:38 PM
Plutôt bien cette vérification de conformité PEP8 (qui n'existe pas sûr Basthon). Par contre j'aime pas trop le f-print à l'arrivée sur la page (je ne montre pas ça à mes élèves avant la Terminale)
September 20, 2026 at 2:25 AM
legibility is king.

please follow pep8 everyone. i beg of you.
November 22, 2023 at 10:24 AM
Not me disregarding PEP8 formatting because I have my own way of typing that I personally prefer and read easier..!
No!
October 2, 2025 at 3:12 PM