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

pyproject: use PyYAML 6.0.1 #1237

Merged
merged 1 commit into from
Jul 21, 2023
Merged

Conversation

jremmet
Copy link
Contributor

@jremmet jremmet commented Jul 19, 2023

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

  • Documentation for the feature
  • Tests for the feature
  • The arguments and description in doc/configuration.rst have been updated
  • Add a section on how to use the feature to doc/usage.rst
  • Add a section on how to use the feature to doc/development.rst
  • PR has been tested
  • Man pages have been regenerated

@jremmet jremmet marked this pull request as ready for review July 20, 2023 06:26
@Bastian-Krause
Copy link
Member

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.

@jremmet
Copy link
Contributor Author

jremmet commented Jul 20, 2023

@Bastian-Krause Should I add a PR for stable-23.0 to?

@Bastian-Krause
Copy link
Member

@Bastian-Krause Should I add a PR for stable-23.0 to?

Much appreciated :)

@jremmet jremmet mentioned this pull request Jul 20, 2023
7 tasks
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 <[email protected]>
@Bastian-Krause
Copy link
Member

Adjusted the commit message slightly, rebased on current master to see if the tests are happy.

@Bastian-Krause Bastian-Krause added this to the v23.1 milestone Jul 20, 2023
@Bastian-Krause Bastian-Krause added fix dependencies Pull requests that update a dependency file labels Jul 20, 2023
@jremmet jremmet closed this Jul 21, 2023
@jremmet jremmet deleted the pyyaml-6.0.1 branch July 21, 2023 06:12
@Bastian-Krause
Copy link
Member

@jremmet Why did you close this PR?

@jremmet jremmet restored the pyyaml-6.0.1 branch July 21, 2023 07:38
@jremmet jremmet reopened this Jul 21, 2023
@jremmet
Copy link
Contributor Author

jremmet commented Jul 21, 2023

@Bastian-Krause Sorry, accidentally cleaned up some branches

@codecov
Copy link

codecov bot commented Jul 21, 2023

Codecov Report

Patch coverage has no change and project coverage change: -0.1 ⚠️

Comparison is base (58ba833) 62.9% compared to head (24ff7b6) 62.9%.

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     

see 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@Emantor Emantor merged commit 6872745 into labgrid-project:master Jul 21, 2023
14 of 15 checks passed
@jremmet jremmet deleted the pyyaml-6.0.1 branch July 21, 2023 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

pyyaml 5.4.1 is broken
3 participants