Skip to content

Conversation

@s-t-e-v-e-n-k
Copy link

Pull Request check-list

Please make sure to review and check all of these items:

  • Do tests and lints pass with this change?
  • Do the CI tests pass with this change (enable it first in your forked repo and wait for the github action build to finish)?
  • Is the new or changed code fully tested?
  • Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
  • Is there an example added to the examples folder (if applicable)?

Description of change

With the minimum Python version now being high enough to drop the usage of the external mock module, switch to unittest.mock everywhere.

@jit-ci
Copy link

jit-ci bot commented Nov 3, 2025

Hi, I’m Jit, a friendly security platform designed to help developers build secure applications from day zero with an MVS (Minimal viable security) mindset.

In case there are security findings, they will be communicated to you as a comment inside the PR.

Hope you’ll enjoy using Jit.

Questions? Comments? Want to learn more? Get in touch with us.

@petyaslavova
Copy link
Collaborator

Hi @s-t-e-v-e-n-k, thank you for your contribution! Can you please check the failing tests - the async tests have some issues with the Mock object? Thanks!

With the minimum Python version now being high enough to drop the usage
of the external mock module, switch to unittest.mock everywhere.

Switch ayncio test_credentials to AsyncMock.
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.

2 participants