time/py-time-machine 3.5.1 NetBSD

3.5.1 Only pass the compiler option -mno-omit-leaf-frame-pointer when the compiler supports it, checked with a tiny probe program. The option is unsupported outside of x86 and ARM64, so this fixes building from source on other architectures, like PowerPC, which failed since the option was added in version 3.3.0. Fix the mocked datetime.date.today() and datetime.datetime.today() to be exact for all supported dates, like datetime.datetime.now(). Previously, they went through a floating-point timestamp, which could round the microseconds, or even the whole day, for dates far in the future. …

3.5.0 (2026-08-25) Support None as a destination for travel() and Traveller.move_to(), meaning the current time. Use this with tick=False to freeze time at the present moment, matching freezegun’s behaviour when freeze_time() is called with no arguments. Extend the Migration CLI to migrate aliased imports: import freezegun as fg and from freezegun import freeze_time as ft, plus calls using such aliases. Extend the Migration CLI to migrate the pytest.mark.freeze_time marker in module-level and class-level pytestmark assignments. Extend the Migration CLI to migrate freeze_time() calls and markers that pass tz_offset with a literal zero value. The argument is dropped, since a zero offset has no effect. …

3.4.0 Publish wheels for Python 3.15. Fix a reference leak in the patched datetime.datetime.utcnow() that occurred when its Python 3.12+ DeprecationWarning was raised as an error, such as under -W error. Each such call leaked a reference to the active traveller object. Extend the Migration CLI to migrate patterns from freezegun’s pytest plugins, pytest-freezegun and pytest-freezer: the freezer fixture and the pytest.mark.freeze_time marker. Also make it migrate freeze_time() context managers that bind the result with as, including converting tick() method calls to shift(). Fix the Migration CLI to handle trailing commas in freeze_time() calls when adding tick=False. Previously, it produced invalid syntax, like travel("2023-01-01",, tick=False). …

3.3.1 Fix small rounding errors in destination calculations. Previously, time-machine computed destinations in floating-point seconds, which could lead to small rounding errors: up to a few hundred nanoseconds for present-day destinations, growing to several microseconds by the year 2500. This change fixes the pipeline to use integer nanoseconds throughout, so time-travel is precise for any supported date. 3.3.0 Support Python 3.15. Mock datetime.date.today() directly, for Python 3.15 support. …