python-libfaketime icon indicating copy to clipboard operation
python-libfaketime copied to clipboard

A fast time mocking alternative to freezegun that wraps libfaketime.

Results 11 python-libfaketime issues
Sort by recently updated
recently updated
newest added

libfaketime has a [FAKETIME_TIMESTAMP_FILE](https://github.com/wolfcw/libfaketime/blob/a04750217b8dc890ac584b92229d8c4a3f23c3e0/README#L217) parameter, that points to a file containing the time to mock: The [README](https://github.com/wolfcw/libfaketime/blob/a04750217b8dc890ac584b92229d8c4a3f23c3e0/README#L424-L433) explains how this works: > Changing the 'x' modifier during run-time > -----------------------------------------...

As discussed in #70 this adds macOS images to the GHA CI. Unfortunalety the macOS tests are failing and I am not sure why.

This patch resolves the issue for me https://github.com/wolfcw/libfaketime/commit/0d964363a4352b7ee358f523c3416d07378d4583 ``` make[1]: Entering directory '/build/libfaketime-2.0.0/libfaketime/vendor/libfaketime/src' gcc -o libfaketime.o -c -std=gnu99 -Wall -Wextra -Werror -Wno-nonnull-compare -fPIC -DPREFIX='"'/usr/local'"' -DLIBDIRNAME='"'/lib/faketime'"' libfaketime.c In file included from...

`libfaketime` recently [updated to 0.9.10](https://github.com/wolfcw/libfaketime/releases/tag/v0.9.10), partly to [fix an issue](https://github.com/wolfcw/libfaketime/issues/357) caused by upgrades to OSX Monterey. We're working around it currently using `freezegun`, but would prefer to drop that and...

`freezegun` allows a datetime spec string to encode a timezone offset like this: ```python >>> with freeze_time('2020-04-15 12:00 +1'): ... print(repr(datetime.datetime.now(tz=dateutil.tz.UTC))) FakeDatetime(2020, 4, 15, 11, 0, tzinfo=tzutc()) ``` This produces...

It's possible for a `tzinfo` object to only have an offset and no named timezone. For example: ```python >>> dateutil.parser.parse('2020-04-12 00:26 +1') datetime.datetime(2020, 4, 12, 0, 26, tzinfo=tzoffset(None, 3600)) ```...

Hello, when upgrading from v2.0.0 to v2.1.0 our suite of pytests which usually takes around 10 minutes, runs for many hours without finishing. I've narrowed it down to the fact...

attempt to fix #81 This is a work in progress.

Running the tests with recent python versions raise a lot of warning of the kind of `DeprecationWarning: datetime.datetime.utcnow() is deprecated and scheduled for removal in a future version. Use timezone-aware...

Currently pytz is used to make datetimes timezone aware. It would be great if support for [zoneinfo](https://docs.python.org/3/library/zoneinfo.html) would be built as this is now part of the Python standard library.