-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Restrict pyparsing version #26153
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
Restrict pyparsing version #26153
Conversation
ccd8386
to
84af240
Compare
@@ -327,7 +327,7 @@ def make_release_tree(self, base_dir, files): | |||
"numpy>=1.21", | |||
"packaging>=20.0", | |||
"pillow>=6.2.0", | |||
"pyparsing>=2.3.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not think we should pin it here yet. The "happy paths" still work, it is the error messages that are broken.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should go in one way or the other.
I am hesitant to pin setup.py and would like a second opinion on that.
The next reviewer should either just merge this as-is or merge my proposed patch and then merge PR.
Anyone can merge on green CI |
sigh, we apparently rely on setup.py's versions on azure. |
I'm going to force-push back to Oscar's last commit and then merge. |
I do not remember exactly which order I added these but most are required... |
I missed the force-pushing in the history, sorry 🐑 |
Thank you @oscargus , sorry for needlessly delaying this. |
…153-on-v3.7.x Backport PR #26153 on branch v3.7.x (Restrict pyparsing version)
PR summary
The simple part of #26152
No documentation as I see this as a way to get the tests to pass again and hopefully it is fixed before next release.
PR checklist