Zac Bentley

@tuteng done

You need an older setuptools version, per [this answer](https://stackoverflow.com/questions/69100275/error-while-downloading-the-requirements-using-pip-install-setup-command-use-2), or a newer PyGithub version in your `pip install` command. The oldest version which contains the fix for this issue is...

I would also love some insight into what was changed that caused this to be closed, or a link to a PR/code/etc. We're affected, and mitigating it (prefork, rabbitmq, celery...

Very possibly wrong, but I don't think the time *zone* affects the disambiguation of the time *parser*. That format would remain ambiguous regardless of zone, I think. The `ParsePreferEu` function...

@wpdonders that solution works, but may break in surprising ways in the presence of `multiprocessing` or other threads. I suggest using the [`asgiref.sync`](https://github.com/django/asgiref) package (specifically `async_to_sync`), which provides the same...

The `--root` argument to `cargo flamegraph` avoids this issue. If `cargo` itself is run with `sudo`, all of its bookkeeping side effects (like the lockfile) before running `flamegraph` are also...

I've never had to do any such thing; I suspect that this may be distro-specific (especially since that directory doesn't exist on my system, and I've never had any trouble...

This would be extremely valuable for several of our use cases. Does `typing_inspect` support the forward resolution needed to get fully reified annotations from an arbitrary callable?

That makes sense. Would it be reasonable to allow users to opt-in to exact type checking? I.e. `check_argument_types(strict_callables=True)` would require supplied callables to be explicitly annotated with compatible types? "Compatible"...

Some prior art (which works for a surprising number of cases given how little code it is) is here: https://github.com/hyroai/gamla/blob/master/gamla/type_safety.py