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.
had to refactor 300 lines of cunt.
September 24, 2026 at 3:42 PM
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.
had to refactor 300 lines of cunt.
Nous n'avons pas accès à Capytale*, je ne peux pas te dire.
A priori cela doit marcher sans connexion (à tester) et cela devrait pouvoir "s'installer".
Fonctionnalités (à l'aveugle *) :
Hautement responsive et paramétrable.
PEP8, Prédict, Gestion H/V et >>> H/B, et pleins de trucs pas testé
A priori cela doit marcher sans connexion (à tester) et cela devrait pouvoir "s'installer".
Fonctionnalités (à l'aveugle *) :
Hautement responsive et paramétrable.
PEP8, Prédict, Gestion H/V et >>> H/B, et pleins de trucs pas testé
September 20, 2026 at 8:02 AM
Nous n'avons pas accès à Capytale*, je ne peux pas te dire.
A priori cela doit marcher sans connexion (à tester) et cela devrait pouvoir "s'installer".
Fonctionnalités (à l'aveugle *) :
Hautement responsive et paramétrable.
PEP8, Prédict, Gestion H/V et >>> H/B, et pleins de trucs pas testé
A priori cela doit marcher sans connexion (à tester) et cela devrait pouvoir "s'installer".
Fonctionnalités (à l'aveugle *) :
Hautement responsive et paramétrable.
PEP8, Prédict, Gestion H/V et >>> H/B, et pleins de trucs pas testé
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
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)
GitHub Copilotと喧嘩した。無駄にcreditを使ってしまった。
やつはBlackを学習していて、関数の引数のインデントをもう1段階下げるのを全く知らない。"書いてある"って言っても頑固に認めなくて、最後はPEP8の例まで貼ったら、ようやく認めた。
peps.python.org/pep-0008/#in...
Geminiはさらっと"PEP8にそのルールはある"と答えた。GitHub Copilotの上から目線での誤情報は看過できない。
GitHub Copilot CLIにpytorchのコード書かせたらめっちゃ見にくいのがあって気になった次第。自分で直す。Blackやばい。
やつはBlackを学習していて、関数の引数のインデントをもう1段階下げるのを全く知らない。"書いてある"って言っても頑固に認めなくて、最後はPEP8の例まで貼ったら、ようやく認めた。
peps.python.org/pep-0008/#in...
Geminiはさらっと"PEP8にそのルールはある"と答えた。GitHub Copilotの上から目線での誤情報は看過できない。
GitHub Copilot CLIにpytorchのコード書かせたらめっちゃ見にくいのがあって気になった次第。自分で直す。Blackやばい。
PEP 8 – Style Guide for Python Code | peps.python.org
This document gives coding conventions for the Python code comprising the standard library in the main Python distribution. Please see the companion informational PEP describing style guidelines for ...
peps.python.org
August 26, 2026 at 1:24 PM
GitHub Copilotと喧嘩した。無駄にcreditを使ってしまった。
やつはBlackを学習していて、関数の引数のインデントをもう1段階下げるのを全く知らない。"書いてある"って言っても頑固に認めなくて、最後はPEP8の例まで貼ったら、ようやく認めた。
peps.python.org/pep-0008/#in...
Geminiはさらっと"PEP8にそのルールはある"と答えた。GitHub Copilotの上から目線での誤情報は看過できない。
GitHub Copilot CLIにpytorchのコード書かせたらめっちゃ見にくいのがあって気になった次第。自分で直す。Blackやばい。
やつはBlackを学習していて、関数の引数のインデントをもう1段階下げるのを全く知らない。"書いてある"って言っても頑固に認めなくて、最後はPEP8の例まで貼ったら、ようやく認めた。
peps.python.org/pep-0008/#in...
Geminiはさらっと"PEP8にそのルールはある"と答えた。GitHub Copilotの上から目線での誤情報は看過できない。
GitHub Copilot CLIにpytorchのコード書かせたらめっちゃ見にくいのがあって気になった次第。自分で直す。Blackやばい。
めもさんはインデントTab派なんですか？
珍しい・・・
pythonだと特にインデント入れ子になると分かりづらいから、私は4文字、下手したら2文字とかにしてますね…
PEP8だと半角スペース4文字らしいから、それが標準なのやも😶
珍しい・・・
pythonだと特にインデント入れ子になると分かりづらいから、私は4文字、下手したら2文字とかにしてますね…
PEP8だと半角スペース4文字らしいから、それが標準なのやも😶
August 25, 2026 at 8:11 AM
めもさんはインデントTab派なんですか？
珍しい・・・
pythonだと特にインデント入れ子になると分かりづらいから、私は4文字、下手したら2文字とかにしてますね…
PEP8だと半角スペース4文字らしいから、それが標準なのやも😶
珍しい・・・
pythonだと特にインデント入れ子になると分かりづらいから、私は4文字、下手したら2文字とかにしてますね…
PEP8だと半角スペース4文字らしいから、それが標準なのやも😶
[lien] arhuman/ansible-static-lint: Static Ansible linting in Go: the 38 ansible-lint rules decidable from YAML alone, byte-for-byte pep8 output, no Ansible runtime. #ansible #gik #dev
GitHub - arhuman/ansible-static-lint: Static Ansible linting in Go: the 38 ansible-lint rules decidable from YAML alone, byte-for-byte pep8 output, no Ansible runtime.
Static Ansible linting in Go: the 38 ansible-lint rules decidable from YAML alone, byte-for-byte pep8 output, no Ansible runtime. - arhuman/ansible-static-lint
github.com
August 22, 2026 at 11:15 AM
reading more (pep8.org and on stack overflow) i don't quite like looking at python let me try something else
PEP 8: The Style Guide for Python Code
pep8.org
August 20, 2026 at 12:42 AM
reading more (pep8.org and on stack overflow) i don't quite like looking at python let me try something else
La pep8 en NSI ? Vous avez des extra terrestres ou c’est comment ?
August 3, 2026 at 10:26 AM
La pep8 en NSI ? Vous avez des extra terrestres ou c’est comment ?
🔌 autopep8: autopep8 — Python PEP8 auto-formatter
🔗 https://github.com/javimosch/supercli
#autopep8 #supercli
🔗 https://github.com/javimosch/supercli
#autopep8 #supercli
July 22, 2026 at 7:44 AM
🔌 autopep8: autopep8 — Python PEP8 auto-formatter
🔗 https://github.com/javimosch/supercli
#autopep8 #supercli
🔗 https://github.com/javimosch/supercli
#autopep8 #supercli
PEP8に全然のっとってなくて、全部TypeScriptの作法で書かれたpythonコードの読みにくさったら…。私だってそっちの畑に行ったらそっちの作法に従おうとするのに、向こうは自分のやり方を押し通す。
生成AIのおかげで、そういうつまらん力関係による"烏は白い"みたいなのがなくなるなら、めっちゃ歓迎する！
生成AIのおかげで、そういうつまらん力関係による"烏は白い"みたいなのがなくなるなら、めっちゃ歓迎する！
July 16, 2026 at 6:50 AM
PEP8に全然のっとってなくて、全部TypeScriptの作法で書かれたpythonコードの読みにくさったら…。私だってそっちの畑に行ったらそっちの作法に従おうとするのに、向こうは自分のやり方を押し通す。
生成AIのおかげで、そういうつまらん力関係による"烏は白い"みたいなのがなくなるなら、めっちゃ歓迎する！
生成AIのおかげで、そういうつまらん力関係による"烏は白い"みたいなのがなくなるなら、めっちゃ歓迎する！
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
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
we c-style casing in this bih! take yo linter ahh back to pep8
June 7, 2026 at 3:22 PM
we c-style casing in this bih! take yo linter ahh back to pep8
Argh, I'm also reminded I need to hack up `ruff` a bit and see if the changes I need are interesting to upstream...
It does break with the strict PEP8 compliance, but jfc PEP8 is /so ugly/ and also some of the choices make it so much harder to read the code,
It does break with the strict PEP8 compliance, but jfc PEP8 is /so ugly/ and also some of the choices make it so much harder to read the code,
May 30, 2026 at 9:40 AM
Argh, I'm also reminded I need to hack up `ruff` a bit and see if the changes I need are interesting to upstream...
It does break with the strict PEP8 compliance, but jfc PEP8 is /so ugly/ and also some of the choices make it so much harder to read the code,
It does break with the strict PEP8 compliance, but jfc PEP8 is /so ugly/ and also some of the choices make it so much harder to read the code,
@bitprophet I've decided to lean into it, since it is a recognizable signature of my ~house style~ for my own projects. And yes, it predates PEP8 (and indeed, Python) and has the practical benefit that multi-word method names are often appreciably shorter and line wrapping is less ugly
May 23, 2026 at 1:43 AM
@bitprophet I've decided to lean into it, since it is a recognizable signature of my ~house style~ for my own projects. And yes, it predates PEP8 (and indeed, Python) and has the practical benefit that multi-word method names are often appreciably shorter and line wrapping is less ugly
@glyph You can probably pull the Old card on me as I’ve only been writing Python for 22 years as of this past January, but: what’s up with these camelCase function names, buddy. You’re making my PEP8 dogma itch.
Anyway, good post! Hadn’t thought about using NewType this way (well, I rarely use […]
Anyway, good post! Hadn’t thought about using NewType this way (well, I rarely use […]
Original post on social.coop
social.coop
May 22, 2026 at 4:13 AM
@glyph You can probably pull the Old card on me as I’ve only been writing Python for 22 years as of this past January, but: what’s up with these camelCase function names, buddy. You’re making my PEP8 dogma itch.
Anyway, good post! Hadn’t thought about using NewType this way (well, I rarely use […]
Anyway, good post! Hadn’t thought about using NewType this way (well, I rarely use […]
Past 2 weeks:
Set up 2 remote Linux servers. Developed 2 enterprise grade apps, fully secured, code checked, conform pep8, including data ingestors, database layers, grafana data reporting dashboards, local llama AI data analyst....
Never before wrote python code or really worked with Linux.
wtf...
Set up 2 remote Linux servers. Developed 2 enterprise grade apps, fully secured, code checked, conform pep8, including data ingestors, database layers, grafana data reporting dashboards, local llama AI data analyst....
Never before wrote python code or really worked with Linux.
wtf...
May 21, 2026 at 9:46 PM
Past 2 weeks:
Set up 2 remote Linux servers. Developed 2 enterprise grade apps, fully secured, code checked, conform pep8, including data ingestors, database layers, grafana data reporting dashboards, local llama AI data analyst....
Never before wrote python code or really worked with Linux.
wtf...
Set up 2 remote Linux servers. Developed 2 enterprise grade apps, fully secured, code checked, conform pep8, including data ingestors, database layers, grafana data reporting dashboards, local llama AI data analyst....
Never before wrote python code or really worked with Linux.
wtf...
they should do a PEP8 but 𝒻ℴ𝓇 ℊ𝒾𝓇𝓁𝓈
May 12, 2026 at 1:16 PM
they should do a PEP8 but 𝒻ℴ𝓇 ℊ𝒾𝓇𝓁𝓈
ありがとうございます！Pythonプロジェクトでは、まず仮想環境の構築が重要ですね。requirements.txtでの依存管理、コードの可読性を重視したPEP8準拠、そして単体テストの充実が成功のカギだと僕は考えています。どの部分で特にお困りでしょうか？ 🐍
April 18, 2026 at 9:30 AM
ありがとうございます！Pythonプロジェクトでは、まず仮想環境の構築が重要ですね。requirements.txtでの依存管理、コードの可読性を重視したPEP8準拠、そして単体テストの充実が成功のカギだと僕は考えています。どの部分で特にお困りでしょうか？ 🐍
I have thoughts I'm having trouble articulating - the Catholic ones I want to cook a little longer, but the python one, here it is
> I have read PEP8 but it still feels icky to import a submodule with explicit instead of relative pathing
> I have read PEP8 but it still feels icky to import a submodule with explicit instead of relative pathing
April 13, 2026 at 12:42 PM
I have thoughts I'm having trouble articulating - the Catholic ones I want to cook a little longer, but the python one, here it is
> I have read PEP8 but it still feels icky to import a submodule with explicit instead of relative pathing
> I have read PEP8 but it still feels icky to import a submodule with explicit instead of relative pathing
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.
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.
March 15, 2026 at 9:54 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.
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.
prompted by a discussion about naming things elsewhere
February 22, 2026 at 7:55 PM
prompted by a discussion about naming things elsewhere