Chris Angelico rosuav at gmail.com
Wed Apr 25 20:03:53 EDT 2018

• Previous message (by thread): [Python-Dev] Visual similarity of "=" and "==" (in context of PEP 572)
• Next message (by thread): [Python-Dev] Is PEP 572 really the most effective way to solve the problems it's targeting?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Thu, Apr 26, 2018 at 9:54 AM, Mikhail V <mikhailwas at gmail.com> wrote:
> Since the discussion about operator choice has completely migrated
> here, I'll put my note also here.
> From the very beginning of PEP 572 discussion I have noticed
> a strange fact - there is told a lot about visual similarity
> of "=" and "==" in Python.
> *Same is told in the PEP 572 (frequently asked question)
>  as the reason for rejection of "=" as operator.*
>
> Hope you get my point here.
> IMO either the PEP 572 should remove or at
> least rephrase this point somehow or, even better,
> concentrate on something more convincing in this regard.

https://www.python.org/dev/peps/pep-0572/#why-not-just-turn-existing-assignment-into-an-expression

Half a century of C programming demonstrates that this is ample argument.

ChrisA

---

• Previous message (by thread): [Python-Dev] Visual similarity of "=" and "==" (in context of PEP 572)
• Next message (by thread): [Python-Dev] Is PEP 572 really the most effective way to solve the problems it's targeting?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list