Paul McGuire

I've looked at the networkx issue, and the issue is due to the tightening up of whitespace-skipping that was pushed out in 3.0.2. This is intentional behavior. To correct in...

If you prefer, pin the current pydot to pyparsing 2.4.7 in a minor release, and then when the pydot maintainers have time/resources for your next pydot major release, open up...

Literal has been in every version of pyparsing as far back as 0.9, so I suspect there is something in your PYTHONPATH that is masking the pyparsing module itself. Do...

Closing this for now - please reopen if you have further notes on how to reproduce this issue. Thanks for using pyparsing!

Before you use the "all the alphas defined in Unicode" option, please check the timing. This property is evaluated lazily, so you don't pay the penalty when you import pyparsing,...

I'm inclined to keep the `replaced_by_pep8` decorator, as it gives a good place to emit a DeprecationWarning when I do the 3.1.0 release.

Looking at this, but late now - will pick up some time tomorrow.

Please don't remove the replaced_by_pep8 decorators. As I said, I'm going to use those to emit DeprecationWarnings starting in pyparsing 3.1.0

That file was removed in pyparsing 3.0.9. There should be no references to that file using the latest pyparsing.

The reference looks like it is coming from pkg_resources, using a vendored version of pyparsing. But ultimately, there is no problem with this warning, since the code doesn't use it...