Removed unneeded spaces before commas and periods.
This commit is contained in:
parent
eb73a3b869
commit
d277ad711a
|
@ -848,8 +848,8 @@ Cursor\ `.scroll`_\ (*value* [, *mode='relative'* ])
|
||||||
left undefined (ideal would be to not move the cursor at all).
|
left undefined (ideal would be to not move the cursor at all).
|
||||||
|
|
||||||
.. Note::
|
.. Note::
|
||||||
This method should use native scrollable cursors, if available
|
This method should use native scrollable cursors, if available,
|
||||||
, or revert to an emulation for forward-only scrollable
|
or revert to an emulation for forward-only scrollable
|
||||||
cursors. The method may raise NotSupportedError_ to signal
|
cursors. The method may raise NotSupportedError_ to signal
|
||||||
that a specific operation is not supported by the database
|
that a specific operation is not supported by the database
|
||||||
(e.g. backward scrolling).
|
(e.g. backward scrolling).
|
||||||
|
|
|
@ -480,7 +480,7 @@ Footnotes and References
|
||||||
http://www.python.org/dev/peps/pep-0219/
|
http://www.python.org/dev/peps/pep-0219/
|
||||||
|
|
||||||
[4] "Iteration Abstraction in Sather"
|
[4] "Iteration Abstraction in Sather"
|
||||||
Murer , Omohundro, Stoutamire and Szyperski
|
Murer, Omohundro, Stoutamire and Szyperski
|
||||||
http://www.icsi.berkeley.edu/~sather/Publications/toplas.html
|
http://www.icsi.berkeley.edu/~sather/Publications/toplas.html
|
||||||
|
|
||||||
[5] http://www.cs.arizona.edu/icon/
|
[5] http://www.cs.arizona.edu/icon/
|
||||||
|
|
|
@ -208,7 +208,7 @@ Here is BaseException as implemented in the 2.x series::
|
||||||
Deprecation of features in Python 2.9 is optional. This is because it
|
Deprecation of features in Python 2.9 is optional. This is because it
|
||||||
is not known at this time if Python 2.9 (which is slated to be the
|
is not known at this time if Python 2.9 (which is slated to be the
|
||||||
last version in the 2.x series) will actively deprecate features that
|
last version in the 2.x series) will actively deprecate features that
|
||||||
will not be in 3.0 . It is conceivable that no deprecation warnings
|
will not be in 3.0. It is conceivable that no deprecation warnings
|
||||||
will be used in 2.9 since there could be such a difference between 2.9
|
will be used in 2.9 since there could be such a difference between 2.9
|
||||||
and 3.0 that it would make 2.9 too "noisy" in terms of warnings. Thus
|
and 3.0 that it would make 2.9 too "noisy" in terms of warnings. Thus
|
||||||
the proposed deprecation warnings for Python 2.9 will be revisited
|
the proposed deprecation warnings for Python 2.9 will be revisited
|
||||||
|
|
|
@ -38,7 +38,7 @@ in detail.
|
||||||
It is not the goal to replace the locale module, to perform
|
It is not the goal to replace the locale module, to perform
|
||||||
internationalization tasks, or accommodate every possible
|
internationalization tasks, or accommodate every possible
|
||||||
convention. Such tasks are better suited to robust tools like
|
convention. Such tasks are better suited to robust tools like
|
||||||
`Babel`_ . Instead, the goal is to make a common, everyday
|
`Babel`_. Instead, the goal is to make a common, everyday
|
||||||
task easier for many users.
|
task easier for many users.
|
||||||
|
|
||||||
.. _`Babel`: http://babel.edgewall.org/
|
.. _`Babel`: http://babel.edgewall.org/
|
||||||
|
|
|
@ -36,7 +36,7 @@ Rationale and Goals
|
||||||
|
|
||||||
This protocol and specification is influenced heavily by the Web
|
This protocol and specification is influenced heavily by the Web
|
||||||
Services Gateway Interface (WSGI) 1.0 standard described in PEP 333
|
Services Gateway Interface (WSGI) 1.0 standard described in PEP 333
|
||||||
[1]_ . The high-level rationale for having any standard that allows
|
[1]_. The high-level rationale for having any standard that allows
|
||||||
Python-based web servers and applications to interoperate is outlined
|
Python-based web servers and applications to interoperate is outlined
|
||||||
in PEP 333. This document essentially uses PEP 333 as a template, and
|
in PEP 333. This document essentially uses PEP 333 as a template, and
|
||||||
changes its wording in various places for the purpose of forming a
|
changes its wording in various places for the purpose of forming a
|
||||||
|
@ -485,7 +485,7 @@ string. Each value is a bytes instance.
|
||||||
bytes instance representing a sequence of URL-encoded segments
|
bytes instance representing a sequence of URL-encoded segments
|
||||||
separated by the slash character (``/``). It is assumed that
|
separated by the slash character (``/``). It is assumed that
|
||||||
``%2F`` characters will be decoded into literal slash characters
|
``%2F`` characters will be decoded into literal slash characters
|
||||||
within ``PATH_INFO`` , as per CGI.
|
within ``PATH_INFO``, as per CGI.
|
||||||
|
|
||||||
``PATH_INFO``
|
``PATH_INFO``
|
||||||
The remainder of the request URL's "path", designating the virtual
|
The remainder of the request URL's "path", designating the virtual
|
||||||
|
@ -495,7 +495,7 @@ string. Each value is a bytes instance.
|
||||||
be a bytes instance representing a sequence of URL-encoded segments
|
be a bytes instance representing a sequence of URL-encoded segments
|
||||||
separated by the slash character (``/``). It is assumed that
|
separated by the slash character (``/``). It is assumed that
|
||||||
``%2F`` characters will be decoded into literal slash characters
|
``%2F`` characters will be decoded into literal slash characters
|
||||||
within ``PATH_INFO`` , as per CGI.
|
within ``PATH_INFO``, as per CGI.
|
||||||
|
|
||||||
``QUERY_STRING``
|
``QUERY_STRING``
|
||||||
The portion of the request URL (in bytes) that follows the ``"?"``,
|
The portion of the request URL (in bytes) that follows the ``"?"``,
|
||||||
|
|
|
@ -192,7 +192,7 @@ without that information, then a ``PyErr_BufferError`` should be raised.
|
||||||
|
|
||||||
This is the default flag state (0). The returned buffer may or may
|
This is the default flag state (0). The returned buffer may or may
|
||||||
not have writable memory. The format will be assumed to be
|
not have writable memory. The format will be assumed to be
|
||||||
unsigned bytes . This is a "stand-alone" flag constant. It never
|
unsigned bytes. This is a "stand-alone" flag constant. It never
|
||||||
needs to be \|'d to the others. The exporter will raise an error if
|
needs to be \|'d to the others. The exporter will raise an error if
|
||||||
it cannot provide such a contiguous buffer of bytes.
|
it cannot provide such a contiguous buffer of bytes.
|
||||||
|
|
||||||
|
|
|
@ -318,7 +318,7 @@ operated in binary.
|
||||||
Decimal computer operation was important enough
|
Decimal computer operation was important enough
|
||||||
that many computers, including the ubiquitous PC, have
|
that many computers, including the ubiquitous PC, have
|
||||||
instructions designed to operate on "binary coded decimal"
|
instructions designed to operate on "binary coded decimal"
|
||||||
(BCD) [5]_ , a representation which devotes 4 bits to each
|
(BCD) [5]_, a representation which devotes 4 bits to each
|
||||||
decimal digit. These instructions date from a time when the
|
decimal digit. These instructions date from a time when the
|
||||||
most strenuous calculations ever performed on many numbers
|
most strenuous calculations ever performed on many numbers
|
||||||
were the calculations actually required to perform textual
|
were the calculations actually required to perform textual
|
||||||
|
|
Loading…
Reference in New Issue