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.

Sign up for GitHub

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

Jump to bottom

bfio==2.3.0 instead of bfio~=2.3.0 #298

Closed
wants to merge 4 commits into from
Closed

bfio==2.3.0 instead of bfio~=2.3.0 #298

wants to merge 4 commits into from

Conversation

SeanLeRoy
Copy link

What does this PR do?

Fixes #<issue_number>

Before submitting

  • Did you make sure title is self-explanatory and the description concisely explains the PR?
  • Did you make sure your PR does only one thing, instead of bundling different changes together?
  • Did you list all the breaking changes introduced by this pull request?
  • Did you test your PR locally with pytest command?
  • Did you run pre-commit hooks with pre-commit run -a command?

Did you have fun?

Make sure you had fun coding 🙃

@SeanLeRoy SeanLeRoy force-pushed the bugfix/try-bfio-2.3.0-specifically branch from 210041a to 399642b Compare October 18, 2023 19:22
@SeanLeRoy SeanLeRoy closed this Oct 20, 2023
@SeanLeRoy SeanLeRoy deleted the bugfix/try-bfio-2.3.0-specifically branch October 20, 2023 18:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@SeanLeRoy