#21337 closed Bug (fixed)
backward incompability for WSGIServerException
| Reported by: | anonymous | Owned by: | nobody |
|---|---|---|---|
| Component: | HTTP handling | Version: | 1.6-beta-1 |
| Severity: | Release blocker | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
https://github.com/django/django/commit/2ca00faa913754cd5860f6e1f23c8da2529c691a
Hi this commit is backward incompatible, I think it would be better to assign socket.error to WSGIServerException name. Or fill documentation and describe this change. I just updated from Beta 1 to RC 1 and non of my servers works.
Change History (6)
comment:1 by , 12 years ago
| Component: | Uncategorized → HTTP handling |
|---|---|
| Severity: | Normal → Release blocker |
| Triage Stage: | Unreviewed → Accepted |
| Type: | Uncategorized → Bug |
| Version: | → 1.6-beta-1 |
comment:2 by , 12 years ago
I'm using devserver (https://github.com/dcramer/django-devserver) and own hooked wsgiserver, changing this Exception just blow up everything. It's simple to change, but this change isn't described anywhere in the docs.
comment:4 by , 12 years ago
| Has patch: | set |
|---|
The pull request is here: https://github.com/django/django/pull/1823
comment:5 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I'm not in a position to check this right now, but if true, the report is a release blocker.