[Python-Dev] PEP 572: Write vs Read, Understand and Control Flow (original) (raw)
Dan Stromberg drsalists at gmail.com
Tue Apr 24 22:50:30 EDT 2018
- Previous message (by thread): [Python-Dev] PEP 572: Write vs Read, Understand and Control Flow
- Next message (by thread): [Python-Dev] PEP 572: Write vs Read, Understand and Control Flow
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Apr 24, 2018 at 2:21 AM, Victor Stinner <vstinner at redhat.com> wrote:
== Write code for babies! ==
Please don't write code for yourself, but write code for babies! :-) These babies are going to maintain your code for the next 5 years, while you moved to a different team or project in the meanwhile. Be kind with your coworkers and juniors!
I don't like the idea of assignment expressions in Python.
“Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.”
- Brian Kernighan
Of the proposed syntaxes, I dislike identifer := expression less, but I'd still rather not see it added.
- Previous message (by thread): [Python-Dev] PEP 572: Write vs Read, Understand and Control Flow
- Next message (by thread): [Python-Dev] PEP 572: Write vs Read, Understand and Control Flow
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]