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

Pin hypothesis at 6.83.0 for python 3.8 #6034

Merged
merged 1 commit into from
Sep 4, 2023

Conversation

andreas-el
Copy link
Contributor

@andreas-el andreas-el commented Sep 4, 2023

Bleeding build is failing due to API mismatch between installed ipython packages and hypothesis for python version 3.8

Issue
Resolves #my_issue

Approach
Short description of the approach

Pre review checklist

  • Read through the code changes carefully after finishing work
  • Make sure tests pass locally (after every commit!)
  • Wait for tests in CI to pass (see "checks" below)
  • Prepare changes in small commits for more convenient review (optional)
  • PR title captures the intent of the changes, and is fitting for release notes.
  • Updated documentation
  • Ensured new behaviour is tested (opened GUI? screenshots? tried workflows?)
  • Commit history is consistent and clean, in line with the contribution guidelines.

Pre merge checklist

  • Added appropriate release note label
  • Commit history is consistent and clean, in line with the contribution
    guidelines
    .

@andreas-el andreas-el self-assigned this Sep 4, 2023
@andreas-el andreas-el added the release-notes:maintenance Automatically categorise as maintenance change in release notes label Sep 4, 2023
@andreas-el andreas-el merged commit a46cb83 into equinor:main Sep 4, 2023
40 checks passed
@andreas-el andreas-el deleted the pin_hypothesis_for_ipython branch September 4, 2023 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-notes:maintenance Automatically categorise as maintenance change in release notes
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants