1. Ian Bicking
  2. wsgi-peps

Commits

mitsuhiko  committed dfeec23

Copyright in PEP XXXX and updates in 0333.

  • Participants
  • Parent commits 0b7736f
  • Branches default

Comments (0)

Files changed (2)

File pep-0333.txt

View file
  • Ignore whitespace
 
     from piglatin import piglatin
     
-    class LatinIter:
+    class LatinIter(object):
 
         """Transform iterated output to piglatin, if it's okay to do so
         
             else:
                 return self._next()
 
-    class Latinator:
+    class Latinator(object):
 
         # by default, don't transform output
         transform = False  
 operatuib us beces
 
 
-Updates
-=======
-
-* Changed the signature of ``environ['wsgi.input'].readline(hint)`` to
-  allow the ``hint`` argument.
-* Removed Python 2.2 compatibility mentionings in the PEP because these
-  versions are no longer in use.
-
 Questions and Answers
 =====================
 
    developers.
 
 
-Proposed/Under Discussion
-=========================
-
-These items are currently being discussed on the Web-SIG and elsewhere,
-or are on the PEP author's "to-do" list:
-
-* Should ``wsgi.input`` be an iterator instead of a file?  This would
-  help for asynchronous applications and chunked-encoding input
-  streams.
-  
-* Optional extensions are being discussed for pausing iteration of an
-  application's ouptut until input is available or until a callback
-  occurs.
-  
-* Add a section about synchronous vs. asynchronous apps and servers,
-  the relevant threading models, and issues/design goals in these
-  areas.
-  
-
 Acknowledgements
 ================
 
 * Mark Nottingham, who reviewed the spec extensively for issues with
   HTTP RFC compliance, especially with regard to HTTP/1.1 features that
   I didn't even know existed until he pointed them out.
+
+
+Updates
+=======
+
+* Changed the signature of ``environ['wsgi.input'].readline(hint)`` to
+  allow the ``hint`` argument.
+* Removed Python 2.2 compatibility mentionings in the PEP because these
+  versions are no longer in use.
+* Removed Jython compatiblity notices because Jython now provides a
+  regular `str` type.
+* mentioned that WSGI 1.0 does not support Python 3
+* clarfified that WSGI 1.0 depends on bytes
+* weakened the rules for buffering and streaming
+* added warning for middleware implementers about `wsgi.file_wrapper`. 
+* Removed references to oudated discussions.
   
 
 References

File pep-XXXX.txt

View file
  • Ignore whitespace
   `iso-8859-1` encoding would be used such that the original character data
   is preserved and as necessary the unicode string can be converted back to
   bytes and thence decoded to unicode again using a different encoding.
-  (Except for URI values, see the URL Decoding section)
+  (Except for URI values, see the URI Decoding section)
 
 - The WSGI input stream ``'wsgi.input'`` contained in the WSGI environment and
   from which request content is read, MUST yield byte strings.
 - The version information in the WSGI environment (`wsgi.version`) is ``(1, 1)``.
 
 
-URL Decoding
+URI Decoding
 ------------
 
 For the keys ``SCRIPT_NAME``, ``PATH_INFO`` (and ``REQUEST_URI`` if
 value is then stored in ``'wsgi.uri_encoding'``.  The application MUST use this
 value to decode the ``'QUERY_STRING'`` as well.
 
-URL Encoding
+URI Encoding
 ------------
 
-If the application encodes URLs it is required to encode the URLs to
+If the application encodes URIs it is required to encode the URLs to
 `utf-8`, independent of the value of the `wsgi.uri_encoding`.
 
 write() deprecated
 The same rule applies for the `exc_info`.  If this parameter is used in
 WSGI 1.1, the server must still handle it, but warn with a deprecation
 warning.
+
+
+Copyright
+=========
+
+This document has been placed in the public domain.
+
+
+
+..
+   Local Variables:
+   mode: indented-text
+   indent-tabs-mode: nil
+   sentence-end-double-space: t
+   fill-column: 70
+   End: