Philip Meier

All of that being said, I'm not sure if I would merge a PR for this right away: there already exists a way for users to hook in third-party components....

If you are up to that, I think sending a PR linking this thread would be fine. Right now our issue / PR tracker is reasonably small that we don't...

Any update on this? Currently we are vendoring the `test/utils.py`, but it would be much nicer to have them in `questionary.test` or the like.

I'll clean up our test code to see what exactly we need and send a PR afterwards.

I'll send a PR if I figure out how this can be solved. My current understanding is that first the `GeneratorExit` is raised and only afterwards the actual error. Thus,...

If I'm reading [this right](https://docs.python.org/3/reference/expressions.html#generator.close) > Raises a `GeneratorExit` at the point where the generator function was paused. [...] If the generator yields a value, a `RuntimeError` is raised. one...

My best guess is that we are hitting a language limitation here: ```py import contextlib def gen(n): for i in range(n): print(f"Before yield {i}") with contextlib.suppress(GeneratorExit): yield i print(f"After yield...

> i propose ensuring subtests transfer generator-exits as is + triggering a warning for the subtest/test I can send a PR for that. What is the preferred way to warn...

We are building documentation on [readthedocs.org](). This build injects some extra files and some additional configuration in existing files. I could potentially ignore the former, but can't really do anything...

> I'm curious why your RTD build actually needs to create a dirty worktree, chances are it doesn't I haven't looked into the actual changes, but rather on the files...