[issue3348] Cannot start wsgiref simple server in Py3k

Antoine Pitrou added the comment: There's a proper patch in #4718, marking this one in duplicate. -- resolution: -> duplicate status: open -> closed superseder: -> wsgiref package totally broken ___ Python tracker

[issue3348] Cannot start wsgiref simple server in Py3k

Phillip J. Eby <[EMAIL PROTECTED]> added the comment: Not any time soon; I don't currently use Py3K and can't even vouch for the correctness of the posted patch within Py3K. (i.e., what really happened to the message class?) Sorry; all I can really do here is clarify WSGI-related questions. __

[issue3348] Cannot start wsgiref simple server in Py3k

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Also reported in #3795. PJE, are you willing to work on this some day? -- nosy: +Walling ___ Python tracker <[EMAIL PROTECTED]> __

[issue3348] Cannot start wsgiref simple server in Py3k

Changes by Antoine Pitrou <[EMAIL PROTECTED]>: -- nosy: +delimy ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing

[issue3348] Cannot start wsgiref simple server in Py3k

Phillip J. Eby <[EMAIL PROTECTED]> added the comment: HTTP is defined as a stream of bytes; the fact that you can specify encodings for headers and content is a different level of the spec. WSGI wants to basically be as transparent a mapping as possible between HTTP and Python data structures

[issue3348] Cannot start wsgiref simple server in Py3k

Matt Giuca <[EMAIL PROTECTED]> added the comment: Wow, I read the WSGI spec. That seems very strange that it says "HTTP does not directly support Unicode, and neither does this interface." Clearly HTTP *does* support Unicode, because it allows you to specify an encoding. I assume then that the I

[issue3348] Cannot start wsgiref simple server in Py3k

Phillip J. Eby <[EMAIL PROTECTED]> added the comment: For the "why Latin-1", read the WSGI spec's explanation of how strings should be handled in Python implementations where 'str' is unicode. I suppose that you *could* make it a text stream with Latin-1 encoding; I'm just not clear on whether

[issue3348] Cannot start wsgiref simple server in Py3k

Matt Giuca <[EMAIL PROTECTED]> added the comment: Are you saying the stream passed to _write SHOULD always be a binary stream, and hence the test case is wrong, because it opens a text stream? (I'm not sure where the stream comes from, but we should guarantee it's a binary stream). Also, why La

[issue3348] Cannot start wsgiref simple server in Py3k

Phillip J. Eby <[EMAIL PROTECTED]> added the comment: The encoding must be latin-1, not utf-8, and the stream must be binary mode, not text. I have no idea how to deal with the test suite, and don't have time at the moment to investigate. ___ Python tracker <

[issue3348] Cannot start wsgiref simple server in Py3k

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- assignee: -> pje nosy: +pje priority: high -> critical ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3348] Cannot start wsgiref simple server in Py3k

Changes by Antoine Pitrou <[EMAIL PROTECTED]>: -- nosy: +pitrou priority: -> high ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python

[issue3348] Cannot start wsgiref simple server in Py3k

New submission from Matt Giuca <[EMAIL PROTECTED]>: The wsgiref "simple server" module has a demo server, which fails to start in Python 3.0 for a bunch of reasons. To verify this, just go into the Lib/wsgiref directory, and run: python3.0 ./simple_server.py (which launches the demo server). Th