Skip to content

Conversation

@kacper-wolkiewicz-reef
Copy link
Collaborator

WIP, because PR in b2sdk must be pulled first (Backblaze/b2-sdk-python#547), release done and library version bumped. Otherwise ready for a review.

Basically the same as Backblaze#1110 but with new commit to use RNG from b2sdk.

Copy link

@olzhasar-reef olzhasar-reef left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR generally looks good.
The only issue is the commit history, could you kindly clean it up (using an interactive rebase probably)? @kacper-wolkiewicz-reef
Commits like the following pollute the history making it less pleasant to work with:

Merge remote-tracking branch 'origin/master' into B2-171-tests-commons
Merge remote-tracking branch 'reef/master' into test-commons-2

Rebase should be preferred when pulling remote changes, especially when it comes to open source projects like Backblaze.

Apart from that, nicely done

fail-fast: false
matrix:
os: ["ubuntu-latest", "ubuntu-24.04-arm", "macos-latest", "windows-latest"]
python-version: ["3.8", "3.9", "3.10", "3.11", "3.12", "3.13", "pypy3.9", "pypy3.10"]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's extremely advisable to extract such changes into a separate PR.
I assume dropping Python 3.8 support was needed to bump the sdk version, but it would have been much better if we had a separate PR for it first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants