Bump time-machine from 2.19.0 to 3.1.0

[dependabot]

Bumps time-machine from 2.19.0 to 3.1.0.

Changelog

Sourced from time-machine's changelog.

3.1.0 (2025-11-21)

• Optimize patching of uuid module. By avoiding using unittest.mock, this small overhead from starting time_machine.travel() has been reduced about 20x, from ~600ns to ~30ns by one benchmark.

  PR [#585](https://github.com/adamchainz/time-machine/issues/585) <https://github.com/adamchainz/time-machine/pull/585>__.

3.0.0 (2025-11-18)

• Remove mocking of time.monotonic() and time.monotonic_ns().

  This mocking caused too many issues, such as causing freezes in asyncio event loops (Issue [#387](https://github.com/adamchainz/time-machine/issues/387) <https://github.com/adamchainz/time-machine/issues/387>), preventing pytest-durations from timing tests correctly (Issue [#505](https://github.com/adamchainz/time-machine/issues/505) <https://github.com/adamchainz/time-machine/issues/505>), and triggering timeouts in psycopg (Issue [#509](https://github.com/adamchainz/time-machine/issues/509) <https://github.com/adamchainz/time-machine/issues/509>__). The root cause here is that mocking the monotonic clock breaks its contract, allowing it to move backwards when it’s meant to only move forwards.

  As an alternative, use |unittest.mock|__ to mock the monotonic function for the specific tested modules that need it. That means that your code should import monotonic() or monotonic_ns() directly, so that your tests can mock it in those places only. For example, if your system under test looks like:

  .. |unittest.mock| replace:: unittest.mock __ https://docs.python.org/3/library/unittest.mock.html

  .. code-block:: python

  # example.py
  from time import monotonic
  def measurement():
  start = monotonic()
  ...
  end = monotonic()
  return end - start
  

  …then your tests can mock monotonic() like this:

  .. code-block:: python

  from unittest import TestCase, mock
  import example
  class MeasurementTests(TestCase):
  def test_success(self):
  with mock.patch.object(example, "monotonic", side_effect=[0.0, 1.23]):
  result = example.measurement()
  assert result == 1.23
  

... (truncated)

Commits

• b9f7500 Version 3.1.0
• 965e906 Optimize patching of uuid module (#585)
• 5d2e8dd Version 3.0.0
• 39ba19f Upgrade cibuildwheel to 3.3.0 (#581)
• 3a0d5dd Raise ValueError from escape_hatch functions when not travelling (#580)
• ac23916 Improve usage documentation (#579)
• d10f000 Parse str destinations with datetime.fromisoformat() first (#578)
• b820451 Reorder changelog
• 48f1af5 Make dateutil an optional dependency (#576)
• 5559f89 Remove Python 3.9 from cibuildwheel target list (#575)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Dependabot attempted to update this pull request, but because the branch dependabot/pip/time-machine-3.1.0 is protected it was unable to do so.