Paul McGuire

If you are not using any of the new features in pyparsing 3.0.9, then you can use 3.0.8 until setuptools/pkg_resources catches up with their vendored version.

Please try updating to the latest version of setuptools - they have had several releases since you opened this ticket, hopefully they have addressed your issue.

@jpp08022002 and @netmonitoring - please add more details on the issue I opened on your behalf on the pypa/setuptools project: https://github.com/pypa/setuptools/issues/3451

Packrat parsing and `indentedBlock` are not going to play well together. `indentedBlock` uses parse actions to update the indent stack, but packrat parsing will not recall parse actions for matches...

I recently wrote a parser using the new IndentedBlock and with left-recursion enabled. LR also uses packrat parsing, so it is indicative to me that the new IndentedBlock class is...

Thanks for raising this - I'm not really happy to see doc duplicated for names like asDict, asList, etc. when as_dict and as_list are the preferred names now. My initial...

Making significant progress on this, including some nicer decorators and adding DeprecationWarnings

I've held off on the DeprecationWarnings for now, I'll enable them in 3.1, to be removed in some later version, maybe not even until 4.0.

Looking at the latest docs, it seems I've still left in a bunch of duplicate doc strings (such as setDebug, setName, etc. on ParserElement and subclasses). If you want, open...

I am less concerned about extra overhead at parser creation time (typically a one-time, upfront cost) than I am about overhead during the actual parse (which is where I get...