Glyph

> Maybe as part of this fix we should move the config from setup.cfg to pyproject.toml fewer moving parts would certainly be better. is this just vestigial or do some...

> Is `klein` designed to be used for high performance applications ? If it's for use in production then it should be as fast as is reasonable.

> I will start investigating where the performance overhead is, and hopefully find some places to optimize. How much of it is happening in Klein vs. e.g. Werkzeug?

> I don't necessarily criticize the existing pages. But, as a developer, I would at least want to have an easier transition into twisted. Yeah, the structure of these documents...

Note that we already have a utility for this, `twisted.trial._dist.stream`. It's already used for adding failures and errors whose associated output sizes may be larger than a single AMP value...

> Then I contiue to work on this Thank you!

Interesting. Let me give that a try…

So, when I do that, I get this: ``` Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/Users/glyph/Library/Application Support/hatch/env/virtual/automat/rI8sZPBT/automat-build/lib/python3.13/site-packages/hatchling/__main__.py", line...

Nope, still present on hatch 1.14.2. To get that second traceback, this is the diff: ```diff diff --git a/pyproject.toml b/pyproject.toml index 90a03ff..c8450ea 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -3,7 +3,6...

@ofek so, I'm pretty sure that `tool.hatch.version` was specifically added because I started getting errors without it.