Nam, I'm not so sure that a "universal parsing library" is possible for the stdlib.
I think one way you could find out what the requirements are is to refactor at least 2 of the existing stdlib modules that you have identified as needing a better parser. Did you find that you could use the same parser code for both? Would it apply to other modules? Barry > On 9 Apr 2019, at 17:06, Nam Nguyen <bits...@gmail.com> wrote: > > On Mon, Apr 8, 2019 at 7:59 AM Christopher Barker <python...@gmail.com > <mailto:python...@gmail.com>> wrote: > > > On Mon, Apr 8, 2019 at 12:02 AM Paul Moore <p.f.mo...@gmail.com > <mailto:p.f.mo...@gmail.com>> wrote: > I would expect that the only reasonable way of getting a parsing > library in the stdlib would be to propose an established one from PyPI > to be moved into the stdlib > > Absolutely -- unlike some proposals, a stand-alone parsing lib could very > easily be developed external to the stdlib. If one gains traction as an > obvious choice, then we can talk about bringing it in. > > All options are still on the table. It is important to closely align the > solution to the goal of making itself available for *internal use* in the > stdlib itself. Having a parser library in the stdlib for *general use* is not > an explicit goal that I am aiming for, just as pgen2 was not intended that > way. Neither should that deter one from being considered. > > Nam > > > -CHB > > > -- > Christopher Barker, PhD > > Python Language Consulting > - Teaching > - Scientific Software Development > - Desktop GUI and Web Development > - wxPython, numpy, scipy, Cython > _______________________________________________ > Python-ideas mailing list > Python-ideas@python.org > https://mail.python.org/mailman/listinfo/python-ideas > Code of Conduct: http://python.org/psf/codeofconduct/
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
