Ran Benita

There is this patch I wrote to test compose support: https://github.com/bluetech/kmscon/tree/compose I updated it now to work with the compose API in the released version of xkbcommon. It works if...

> A malicious client who bypasses the disabled button and attempts to submit the login for, will receive a HTTP response with an error code > 400. What prevents the...

The CI failure is unrelated: `hudson.plugins.git.GitException: Failed to fetch from git://github.com/django/django.git`.

I rebased and removed a bad commit; the CI passed now.

> Based on my comments, are we sure that there isn't some untested case that has changed? In your example `lazy(lambda: 1, str)()`, the function returns an `int` but the...

> Yeah, that was a sloppy example, but it "worked" before. I don't think bug-compatibility should be kept here, especially since making this mistake is very visible so it's unlikely...

I couldn't resist adding another commit, "Changed __proxy__ to prepare eagerly." (the commit message explains).

Rebased. The two conflicts were with 577f2338f16bea055abc49c5a43fa3ecb05dffc8 and 775b796d8d13841059850d73986d5dcc2e593077 (cc @hramezani) which were not semantic conflicts, except for the test which is now passing because having both `str` and `bytes`...

Hmm just noticed a regression of sorts - now sphinx shows a bunch of private constructors (e.g. [here](https://pytest--9248.org.readthedocs.build/en/9248/reference/reference.html#pytest.Cache) - search for `_ispytest` in the API Reference) where previously it didn't....

@hoefling Thanks for looking at this. > Setting it to autodoc_typehints_description_target = "documented" and explicitly stating what init parameters are documented in the class docstring should help. Seems like we're...