3 ms·

Sorry can you EILI(have 3ish years of python experience but rarely get this far into the weeds.) What is an example of being more incomprehensible? >Python co

Sorry can you EILI(have 3ish years of python experience but rarely get this far into the weeds.) What is an example of being more incomprehensible? >Python code doesn't even work with Python code Is this statement a function of the 2 > 3 transition.

brianjlogan 6y ago
Probably additions like the Walrus operator that "complicate" the syntax and negate the "Zen" of Python by having one right way of doing something. Migrating away from the pseudocodeness of Python. Just a guess though I have about the same experience as you.
pansa2 6y ago
> What is an example of being more incomprehensible? Python's type hints, in particular, have added a huge amount of complexity to the last few versions of the language.
- deleted 6y ago
  [deleted]
- comfydragon 6y ago
  Type annotations are completely optional though. It's possible to write Python that targets 3.5 and 3.8 at the same time.
  - pansa2 6y ago
    The core developers made data classes unnecessarily dependent on type annotations, which made me worry that annotations would become less-and-less optional over time. Fortunately, that doesn't seem to be happening. However, the numerous (very long) typing-related PEPs are definitely making the language larger and more complex. Also, any code that uses annotations is more verbose and less like what I want from Python - executable pseudocode.
    - pansa2 6y ago
      > Fortunately [annotations becoming less-and-less optional over time] doesn't seem to be happening. On the other hand, Guido himself recently said "new stdlib code should be written with annotations inline" [0] whereas the core developers original position was "it will be the choice of the author of new stdlib modules whether and how to use type hints" [1], or even "We will not be putting type annotations anywhere in the stdlib" [2]. [0] https://pyfound.blogspot.com/2020/04/the-path-forward-for-typing-python.html https://pyfound.blogspot.com/2020/04/the-path-forward-for-ty... [1] https://mail.python.org/archives/list/python-dev@python.org/message/F54JYUKL3MVIN3MS5NE66DGJSW22XFUU/ https://mail.python.org/archives/list/python-dev@python.org/... [2] https://mail.python.org/archives/list/python-dev@python.org/message/3JXOMQR7KSVZTFWL3QUJMUGBOYB6TETL/ https://mail.python.org/archives/list/python-dev@python.org/...

brianjlogan 6y ago

Probably additions like the Walrus operator that "complicate" the syntax and negate the "Zen" of Python by having one right way of doing something. Migrating away from the pseudocodeness of Python. Just a guess though I have about the same experience as you.

pansa2 6y ago

> What is an example of being more incomprehensible? Python's type hints, in particular, have added a huge amount of complexity to the last few versions of the language.

deleted 6y ago
[deleted]
comfydragon 6y ago
Type annotations are completely optional though. It's possible to write Python that targets 3.5 and 3.8 at the same time.
- pansa2 6y ago
  The core developers made data classes unnecessarily dependent on type annotations, which made me worry that annotations would become less-and-less optional over time. Fortunately, that doesn't seem to be happening. However, the numerous (very long) typing-related PEPs are definitely making the language larger and more complex. Also, any code that uses annotations is more verbose and less like what I want from Python - executable pseudocode.
  - pansa2 6y ago
    > Fortunately [annotations becoming less-and-less optional over time] doesn't seem to be happening. On the other hand, Guido himself recently said "new stdlib code should be written with annotations inline" [0] whereas the core developers original position was "it will be the choice of the author of new stdlib modules whether and how to use type hints" [1], or even "We will not be putting type annotations anywhere in the stdlib" [2]. [0] https://pyfound.blogspot.com/2020/04/the-path-forward-for-typing-python.html https://pyfound.blogspot.com/2020/04/the-path-forward-for-ty... [1] https://mail.python.org/archives/list/python-dev@python.org/message/F54JYUKL3MVIN3MS5NE66DGJSW22XFUU/ https://mail.python.org/archives/list/python-dev@python.org/... [2] https://mail.python.org/archives/list/python-dev@python.org/message/3JXOMQR7KSVZTFWL3QUJMUGBOYB6TETL/ https://mail.python.org/archives/list/python-dev@python.org/...