1. Nozomu Kaneko
  2. knzm.bitbucket.org-src-patches

Commits

Nozomu Kaneko  committed 6950d9f

remove original footnote link

  • Participants
  • Parent commits f79a312
  • Branches default

Comments (0)

Files changed (3)

File footnote.diff

View file
+# HG changeset patch
+# Parent cd196712b3e3ac9a7e893ed514f828651de9ed72
+diff -r cd196712b3e3 -r dc89be7bce98 pep-0333-ja.txt
+--- a/pep-0333-ja.txt	Sun Feb 13 23:55:11 2011 +0900
++++ b/pep-0333-ja.txt	Mon Feb 14 00:13:43 2011 +0900
+@@ -67,7 +67,7 @@
+ 
+    Python currently boasts a wide variety of web application frameworks,
+    such as Zope, Quixote, Webware, SkunkWeb, PSO, and Twisted Web -- to
+-   name just a few [1]_.  This wide variety of choices can be a problem
++   name just a few [1].  This wide variety of choices can be a problem
+    for new Python users, because generally speaking, their choice of web
+    framework will limit their choice of usable web servers, and vice
+    versa.
+@@ -929,7 +929,7 @@
+ 
+    The ``environ`` dictionary is required to contain these CGI
+    environment variables, as defined by the Common Gateway Interface
+-   specification [2]_.  The following variables **must** be present,
++   specification [2].  The following variables **must** be present,
+    unless their value would be an empty string, in which case they
+    **may** be omitted, except as otherwise noted below.
+ 
+@@ -1074,7 +1074,7 @@
+    A server or gateway **should** attempt to provide as many other CGI
+    variables as are applicable.  In addition, if SSL is in use, the server
+    or gateway **should** also provide as many of the Apache SSL environment
+-   variables [5]_ as are applicable, such as ``HTTPS=on`` and
++   variables [5] as are applicable, such as ``HTTPS=on`` and
+    ``SSL_PROTOCOL``.  Note, however, that an application that uses any CGI
+    variables other than the ones listed above are necessarily non-portable
+    to web servers that do not support the relevant extensions.  (For
+@@ -1712,7 +1712,7 @@
+ .. container:: original
+ 
+    And, if the server and client both support HTTP/1.1 "chunked
+-   encoding" [3]_, then the server **may** use chunked encoding to send
++   encoding" [3], then the server **may** use chunked encoding to send
+    a chunk for each ``write()`` call or string yielded by the iterable,
+    thus generating a ``Content-Length`` header for each chunk.  This
+    allows the server to keep the client connection alive, if it wishes
+@@ -2338,7 +2338,7 @@
+    However, because WSGI servers and applications do not communicate via
+    HTTP, what RFC 2616 calls "hop-by-hop" headers do not apply to WSGI
+    internal communications.  WSGI applications **must not** generate any
+-   "hop-by-hop" headers [4]_, attempt to use HTTP features that would
++   "hop-by-hop" headers [4], attempt to use HTTP features that would
+    require them to generate such headers, or rely on the content of
+    any incoming "hop-by-hop" headers in the ``environ`` dictionary.
+    WSGI servers **must** handle any supported inbound "hop-by-hop" headers

File series

View file
 work.diff
+footnote.diff

File work.diff

View file
 # User Nozomu Kaneko <nozom.kaneko@gmail.com>
 # Date 1297608911 -32400
 # Node ID 638447c6af64989c9f6e70e8e205e6a150b90f14
-# Parent  a94c348518684ec0e309378734424ef09948aa3c
+# Parent a94c348518684ec0e309378734424ef09948aa3c
 integrate with sphinx
 
-diff -r a94c34851868 -r 638447c6af64 index.txt
+diff -r a94c34851868 index.txt
 --- a/index.txt	Sun Feb 13 23:33:39 2011 +0900
-+++ b/index.txt	Sun Feb 13 23:55:11 2011 +0900
++++ b/index.txt	Mon Feb 14 00:09:03 2011 +0900
 @@ -11,6 +11,9 @@
  .. toctree::
     :maxdepth: 1
  Indices and tables
  ==================
  
-diff -r a94c34851868 -r 638447c6af64 pep-0333-ja.txt
+diff -r a94c34851868 pep-0333-ja.txt
 --- a/pep-0333-ja.txt	Sun Feb 13 23:33:39 2011 +0900
-+++ b/pep-0333-ja.txt	Sun Feb 13 23:55:11 2011 +0900
++++ b/pep-0333-ja.txt	Mon Feb 14 00:09:03 2011 +0900
 @@ -1,26 +1,42 @@
 -PEP: 333
 -Title: Python Web Server Gateway Interface v1.0
  
  しかし、既存のアプリケーションやフレームワークは、おそらくただ一つの設
  定値を、それらのアプリケーションまたはフレームワーク特有の構成ファイル
-@@ -2355,13 +2680,17 @@
+@@ -2355,12 +2680,16 @@
  URL 再構築
  
  
 +   may do so using the following algorithm, contributed by Ian Bicking:
  
  アプリケーションがリクエストの完全な URL を再構築したいなら、Ian
- Bicking によって寄稿された以下のアルゴリズムが使用できるかもしれない::
- 
- 
+-Bicking によって寄稿された以下のアルゴリズムが使用できるかもしれない::
+-
++Bicking によって寄稿された以下のアルゴリズムが使用できるかもしれない:
++
++
 +.. code-block:: python
-+
+ 
      from urllib import quote
      url = environ['wsgi.url_scheme']+'://'
- 
 @@ -2383,10 +2712,12 @@
          url += '?' + environ['QUERY_STRING']
  
  
    Mark Nottingham は、HTTP RFC の規則に則っているかを広範囲でレビューし
    てくれた。特に、 HTTP/1.1 の機能の数々は、彼が指摘するまで私は存在す
-diff -r a94c34851868 -r 638447c6af64 pep-3333-ja.txt
+diff -r a94c34851868 pep-3333-ja.txt
 --- a/pep-3333-ja.txt	Sun Feb 13 23:33:39 2011 +0900
-+++ b/pep-3333-ja.txt	Sun Feb 13 23:55:11 2011 +0900
++++ b/pep-3333-ja.txt	Mon Feb 14 00:09:03 2011 +0900
 @@ -1,3 +1,7 @@
 +============================================================
 +PEP 3333: Python Web Server Gateway Interface v1.0.1