spumer

Yea, i'm working on refactoring. Сurrent implementation has a lot of troubles with changes detection

Can you post your models which trigger this error?

Hi. Sure, i will check it

@jllorencetti can we accept this PR? This really good feature

Any workaround for that case? I think https://github.com/jllorencetti/pytest-deadfixtures/pull/23 can help solve it manually (per project) And will be greatfull make support setup.cfg like [per-file-ignore](https://flake8.pycqa.org/en/latest/user/options.html?#cmdoption-flake8-per-file-ignores) ``` used-fixtures-per-file = tests/conftest.py:async_wrapper,regular_wrapper ```

>I'm not sure about your quote of the RFC or your Sentry report, but I guess you were saying we shouldn't allow local_addr=("192.168.0.2", 0)? No, RFC references for `UDPTransport.sendto(DATA, (IP,...

i'm encountered the same issue: When default timezone is UTC ```python with freeze_time('2017-11-24T10:54:36.762+05:00', tz_offset=5): print(datetime.datetime.now().astimezone()) 2017-11-24 10:54:36.762000+00:00 ``` I expect output should be `2017-11-24 05:54:36.762000+00:00`

In my case of course i should not use `tz_offset` argument. But i think it will be great respect tz_offset at parsing time (in `__init__`). Then we will have correct...

My final workaround for `.astimezone()`: **conftest.py** ```python def patched_freezgun_astimezone(self, tz=None): from freezegun.api import datetime_to_fakedatetime from freezegun.api import real_datetime if tz is None: from freezegun.api import tzlocal tz = tzlocal() real...

And we can workaround `.now()` by using `.astimezone()`: ```python def patched_freezegun_now(cls, tz=None): from freezegun.api import datetime_to_fakedatetime from freezegun.api import real_datetime now = cls._time_to_freeze() or real_datetime.now() result = now + cls._tz_offset()...