Skip to content

Conversation

@timhoffm
Copy link
Member

PR Summary

Pyparsing 3.0.0 introduced some backward-incompatible changes. As a result, we pinned it in #21445 + #21446.

Let's see if this is fixed in the more recent versions of pyparsing.

@timhoffm timhoffm marked this pull request as draft October 28, 2021 20:47
@timhoffm
Copy link
Member Author

timhoffm commented Oct 28, 2021

@ptmcg

with pyparsing 3.0.3 we see shifts in some math formulas: Can it be that this is caused by the change to pyparsing >=3?

e.g. for r"$\sqrt[3]{x}=5$"

got:
grafik
expected:
grafik
diff:
grafik

@ptmcg
Copy link

ptmcg commented Oct 28, 2021

It looks like a leading space was included or not included (I can't tell which is the before and which is the after in your diff). I'm trying to test your parser in isolation, but I keep having to pull in more and more code. Is there a way to test without doing the whole Anaconda installation?

@timhoffm
Copy link
Member Author

Have you used the environment.yml from the repository base?

@anntzer anntzer mentioned this pull request Oct 29, 2021
7 tasks
@timhoffm
Copy link
Member Author

Superseded by #21501.

@timhoffm timhoffm closed this Nov 11, 2021
@QuLogic QuLogic deleted the pyparsing-tests branch November 16, 2021 02:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants