-
Notifications
You must be signed in to change notification settings - Fork 180
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
pyproject: use PyYAML 6.0.1 #1237
Conversation
For master, we probably want to set the minimum version to 6.0.1. For stable-23.0, we want to pin to that exact version. |
@Bastian-Krause Should I add a PR for stable-23.0 to? |
Much appreciated :) |
With the release of Cython3 the build of PyYAML 5.4.1 is broken [1]. There seems to be no plan to fix 5.4.x branch [2]. Tox tests and a real world example runs fine with 6.0.1 [1] yaml/pyyaml#724 [2] yaml/pyyaml#728 Signed-off-by: Jan Remmet <j.remmet@phytec.de>
761cbb1
to
24ff7b6
Compare
Adjusted the commit message slightly, rebased on current master to see if the tests are happy. |
@jremmet Why did you close this PR? |
@Bastian-Krause Sorry, accidentally cleaned up some branches |
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## master #1237 +/- ##
========================================
- Coverage 62.9% 62.9% -0.1%
========================================
Files 159 159
Lines 11751 11756 +5
========================================
- Hits 7399 7397 -2
- Misses 4352 4359 +7 ☔ View full report in Codecov by Sentry. |
With the release of Cython3 the build of PyYAML 5.4.1 is broken [1]. There seems to be no plan to fix 5.4.x branch [2]. Tox tests and a real world example runs fine with 6.0.1
[1] yaml/pyyaml#724
[2] yaml/pyyaml#728
fixes #1236
tested also on origin/stable-23.0 with 6.0.1
unit tests are failing because of #1238
Description
Checklist