Rémi Cardona

Feel free to do the rebase yourself and post a link to it here, if you're really in a hurry that's probably the best course of action. Others may pitch...

Asynctest partially works on 3.8 but fails almost completely on 3.9, see https://github.com/Martiusweb/asynctest/issues/132 and https://github.com/Martiusweb/asynctest/issues/144. So it's much bigger than just the use of `@coroutine`.

https://github.com/Martiusweb/asynctest/issues/132 TL;DR parts of asynctest are broken on 3.8 and newer

My experience with `gc` tells me that adding a call to `collect()` is a bad idea. First of all, I think this would be quite unexpected by a lot of...

Yeah, I hit that one. It breaks TestCase classes where `forbid_get_event_loop` is enabled. Bit of a bummer.

based on @IaroslavR 's comment, I wrote the following context manager which does the job in my testsuite: ```python @contextlib.contextmanager def mock_tz(new_tz): old_tz = os.environ.get('TZ') os.environ['TZ'] = new_tz time.tzset() try:...

Hi folks, I'm thrilled to report that this fixture works as intended with my work codebase. Until a new release is cut out with this PR, I've vendored the fixture....

Hi folks, is there anything I can do to help get the ball rolling on this PR? We've been using it successfully for a few months now, it's rock solid...

Hi folks, I've been revisiting old TODOs at work and this issue popped up. I was thinking, to help merging this PR, maybe an "experimental" disclaimer/tag in the doc could...

Same issue when using Django's "Q objects" https://docs.djangoproject.com/en/3.1/topics/db/queries/#complex-lookups-with-q 2 Q objects `|`-ed or `&`-ed together is fine, 3 or more breaks pylint. We're getting hundreds of errors as Q objects...