Skip to content
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

Merged
merged 1 commit into from
Jun 20, 2023
Merged

Restrict pyparsing version #26153

merged 1 commit into from
Jun 20, 2023

Conversation

oscargus
Copy link
Contributor

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

@oscargus oscargus added the PR: dependencies Pull requests that update a dependency file label Jun 19, 2023
@oscargus oscargus added this to the v3.7.2 milestone Jun 19, 2023
@oscargus oscargus added the Release critical For bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions. label Jun 19, 2023
@oscargus oscargus force-pushed the pyparsing branch 3 times, most recently from ccd8386 to 84af240 Compare June 19, 2023 14:21
@@ -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",
Copy link
Member

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.

setup.py Show resolved Hide resolved
Copy link
Member

@tacaswell tacaswell left a 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.

@ksunden
Copy link
Member

ksunden commented Jun 20, 2023

Anyone can merge on green CI

@tacaswell
Copy link
Member

sigh, we apparently rely on setup.py's versions on azure.

@tacaswell
Copy link
Member

I'm going to force-push back to Oscar's last commit and then merge.

@oscargus
Copy link
Contributor Author

I do not remember exactly which order I added these but most are required...

@tacaswell
Copy link
Member

I missed the force-pushing in the history, sorry 🐑

@tacaswell tacaswell merged commit ebc7ade into matplotlib:main Jun 20, 2023
54 of 57 checks passed
meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull request Jun 20, 2023
@oscargus oscargus deleted the pyparsing branch June 20, 2023 19:24
@tacaswell
Copy link
Member

Thank you @oscargus , sorry for needlessly delaying this.

QuLogic added a commit that referenced this pull request Jun 20, 2023
…153-on-v3.7.x

Backport PR #26153 on branch v3.7.x (Restrict pyparsing version)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: dependencies Pull requests that update a dependency file Release critical For bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants