4 ms·

Does anybody have interesting, practical, examples of the consequences of switching to a PEG parser? I think this is a rather innovative choice among the mains

• xrisk 6y ago
  Take a look at the PEP - https://www.python.org/dev/peps/pep-0617/ https://www.python.org/dev/peps/pep-0617/
  • pizza234 6y ago
    I'm aware of that, but I was curious about real-world effects (the PEP is mostly theoretical).
    • coldtea 6y ago
      The real world effects, aside from a little slower parsing speed iirc, would only be noticed by the compiler / parser writers. Mainly making it easier to do syntax extensions... For Python devs there will be no real-world effects...
      • pansa2 6y ago
        > Mainly making it easier to do syntax extensions... Yes, AFAICT the main reason for the parser change is to enable the pattern matching feature [0] that’s likely coming in 3.10. [0] https://www.python.org/dev/peps/pep-0634/ https://www.python.org/dev/peps/pep-0634/
        • kzrdude 6y ago
          Here is a readable PEP * https://www.python.org/dev/peps/pep-0635/ https://www.python.org/dev/peps/pep-0635/
          • pansa2 6y ago
            PEP 622 has been superseded by 634, 635 and 636.
            • kzrdude 6y ago
              oh, thanks. Either way, 634 is not particularly enlightening. 635 it is..