Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

MNT: Unpin pyparsing, xfail error message tests for pyparsing 3.1.0#26431

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
jklymak merged 1 commit intomatplotlib:mainfromksunden:pyparsing_pin
Aug 1, 2023

Conversation

ksunden
Copy link
Member

PR summary

Closes#26152

May require backporting a portion of#26198 to the 3.7 branch if we wish to have a 3.7.3.
(specifically the part where token, placeable, and auto_delim are excluded fromsetName)

PR checklist

@ksunden
Copy link
MemberAuthor

I did run locally with pyparsing 3.1.0 to ensure that the tests xfailed as desired. CI does not have anything that would pin that specific version, so not tested automatically.

I initially ran only the mathtext subset, found that there are two more intest_text that need to be xfailed when running the full set with 3.1.0, fixing now.

May require backporting a portion ofmatplotlib#26198 to the 3.7 branch if we wish to have a 3.7.3.(specifically the part where token, placeable, and auto_delim are excluded from setName)
@ksundenksunden added the Release criticalFor bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions. labelAug 1, 2023
@ksundenksunden added this to thev3.7.3 milestoneAug 1, 2023
@ksunden
Copy link
MemberAuthor

Labeling as 3.7.3. While the backport shouldn't fail, we probably do want to include the lines from#26198 in there.

@@ -19,7 +19,7 @@ dependencies:
- pillow>=6.2
- pybind11>=2.6.0
- pygobject
- pyparsing!=3.1.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.

Do you not need to exclude the version that doesn't work?

@tacaswell
Copy link
Member

Given that we have the xfails on the tests and functionally the issue is that error messages on badly formatted strings (not failing for correctly formatted strings) I think it is OK to not put in any exclusionary pins.

@jklymakjklymak merged commit5bdac1d intomatplotlib:mainAug 1, 2023
meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull requestAug 1, 2023
QuLogic added a commit that referenced this pull requestAug 3, 2023
…431-on-v3.7.xBackport PR#26431 on branch v3.7.x (MNT: Unpin pyparsing, xfail error message tests for pyparsing 3.1.0)
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@tacaswelltacaswelltacaswell approved these changes

@jklymakjklymakjklymak approved these changes

Assignees
No one assigned
Labels
Release criticalFor bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions.
Projects
None yet
Milestone
v3.7.3
Development

Successfully merging this pull request may close these issues.

[Bug]: Pyparsing 3.1 breaks tests
4 participants
@ksunden@tacaswell@blshkv@jklymak

[8]ページ先頭

©2009-2025 Movatter.jp