[issue35565] Add detail to an assertion failure message in wsgiref

Change by Raymond Hettinger : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue35565] Add detail to an assertion failure message in wsgiref

Raymond Hettinger added the comment: New changeset b6af23ebf9d6667fa222e804f045735289b4527f by Raymond Hettinger in branch 'master': Revert "bpo-35565: Add detail to assertion failure message in wsgiref" (GH-11317) https://github.com/python/cpython/commit/b6af23ebf9d6667fa222e804f045735289b4

[issue35565] Add detail to an assertion failure message in wsgiref

Change by Raymond Hettinger : -- pull_requests: +10565 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue35565] Add detail to an assertion failure message in wsgiref

Change by Raymond Hettinger : -- pull_requests: +10565, 10566, 10567 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue35565] Add detail to an assertion failure message in wsgiref

Change by Raymond Hettinger : -- pull_requests: +10565, 10566 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35565] Add detail to an assertion failure message in wsgiref

Raymond Hettinger added the comment: New changeset 5ef4fc241aea6759ef3f55b1ef564aebc492a0db by Raymond Hettinger (Cheryl Sabella) in branch 'master': bpo-35565: Add detail to assertion failure message in wsgiref (GH-11293) https://github.com/python/cpython/commit/5ef4fc241aea6759ef3f55b1ef564

[issue35565] Add detail to an assertion failure message in wsgiref

Change by Cheryl Sabella : -- keywords: +patch pull_requests: +10523 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-

[issue35565] Add detail to an assertion failure message in wsgiref

New submission from Raymond Hettinger : On line 236 in Lib/wsgiref/handlers.py, we get the assertion message, "Hop-by-hop headers not allowed". That message should should show the *name* and *value* that triggered the failure. Otherwise, it is difficult to know which header caused the pro