You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[ENH]: Parser errors should mention that commands do not exist #26732
After digging through a few rabbit holes (e.g., reverting from pyparsing 3.1.x to 3.0.9), it turns out that stackrel had been deprecated all the way back in 3.1.0.
Proposed solution
It would be nice if, instead of an error like this, it says something like 'stackrel is not a recognized command". Even better would be to have the stackrel deprecation bring up a warning/error at this point.
This will be fixed with 3.7.3 (when released), though also requires pyparsing !=3.1.0 for the error message. We decided not to enforce that restriction for install since working code continued to work, but did add some xfails to our test suite with the affected combinations.
Since this is fixed on main/the release branch, I will close this
Activity
ksunden commentedon Sep 11, 2023
This is a result of a change to pyparsing that I'm pretty sure we have largely fixed, though it did incur changes in both mpl and pyparsing.
The happy path always worked, just there are some combinations that get less helpful error messages like this.
On main I get:
xref:
This will be fixed with 3.7.3 (when released), though also requires pyparsing !=3.1.0 for the error message. We decided not to enforce that restriction for install since working code continued to work, but did add some xfails to our test suite with the affected combinations.
Since this is fixed on main/the release branch, I will close this
mathstuf commentedon Sep 11, 2023
Thanks for the info. Can this get a 3.7.3 milestone too so that it gets tracked for others searching?