-
-
Notifications
You must be signed in to change notification settings - Fork 274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pyparsing 3.0.2 broke pydot #319
Comments
I'm looking at this now - can you post the expected output for both of these, so that if I resolve one part of the issue, I'll know if there is more to do, or the expected results were returned? Thanks for checking this out so quickly! |
Might not be super useful but here are the expected outputs: In [1]: import pydot
In [2]: pydot.graph_from_dot_data("graph G { b1 [label=<Hello World>]; }")
Out[2]: [<pydot.Dot at 0x7f8c19cf8430>]
In [3]: pydot.graph_from_dot_data("""
...: graph G {
...: b1 [label=<
...: We are the knights who say <BR/># Ni
...: >];
...: }
...: """)
Out[3]: [<pydot.Dot at 0x7f8c19d0fe80>] pydot has some dependencies on graphviz, I've installed it through conda. I'm running this version of graphviz.
|
Yes, the pydot.Dot reprs aren't helping me much. Testing the parser in isolation (with some changes in pyparsing), I get these outputs:
I can guess that the second one looks right, but the first one omits "# Ni" - is that the expected behavior? Unfortunately, my pyparsing changes perturb some other behavior, so I'm not totally out of the woods. But it looks like I'm in the right place. |
It looks like I have to undo a small performance optimization, but otherwise, all regression tests pass (plus the new ones added from this week to reference parsers that use pyparsing). |
@ptmcg you are right about the "# Ni" it is expected at the moment (see open issue pydot/pydot#235). I shouldn't have used that example, my bad. |
Fixed in 3.0.3, just pushed to pypi. |
I can confirm 3.0.3 is working great for my use cases. Feel free to close this issue. |
Hi,
I just stumbled on this issue with pyparsing 3.0.2 (I can confirm 2.4.7, 3.0.0, and 3.0.1 were fine).
Note the leading whitespaces in the string.Here's a simpler minimal example:
The text was updated successfully, but these errors were encountered: