mirror of
https://github.com/python/cpython.git
synced 2025-07-24 11:44:31 +00:00
Merged revisions 72661,72675-72677,72679,72712,72801,72820 via svnmerge from
svn+ssh://pythondev@svn.python.org/python/trunk ........ r72661 | georg.brandl | 2009-05-15 10:03:03 +0200 (Fr, 15 Mai 2009) | 1 line Fix example output for doctest-like demos. ........ r72675 | georg.brandl | 2009-05-16 13:13:21 +0200 (Sa, 16 Mai 2009) | 1 line #6034: clarify __reversed__ doc. ........ r72676 | georg.brandl | 2009-05-16 13:14:46 +0200 (Sa, 16 Mai 2009) | 1 line #6025: fix signature of parse(). ........ r72677 | georg.brandl | 2009-05-16 13:18:55 +0200 (Sa, 16 Mai 2009) | 1 line #6009: undocument default argument of Option as deprecated. ........ r72679 | georg.brandl | 2009-05-16 13:24:41 +0200 (Sa, 16 Mai 2009) | 1 line Fix about and bugs pages to match real workflow. ........ r72712 | georg.brandl | 2009-05-17 10:55:00 +0200 (So, 17 Mai 2009) | 1 line #5935: mention that BROWSER is looked for in PATH. ........ r72801 | georg.brandl | 2009-05-20 20:31:14 +0200 (Mi, 20 Mai 2009) | 1 line #6055: refer to "sqlite3" consistently. ........ r72820 | georg.brandl | 2009-05-22 09:23:32 +0200 (Fr, 22 Mai 2009) | 1 line Use raise X(y). ........
This commit is contained in:
parent
0c31562a91
commit
8a1e4c4b64
9 changed files with 44 additions and 31 deletions
|
@ -338,9 +338,9 @@ within *IDLE* or *PythonWin*::
|
|||
>>> printf("Hello, %s\n", "World!")
|
||||
Hello, World!
|
||||
14
|
||||
>>> printf("Hello, %S", u"World!")
|
||||
>>> printf("Hello, %S\n", u"World!")
|
||||
Hello, World!
|
||||
13
|
||||
14
|
||||
>>> printf("%d bottles of beer\n", 42)
|
||||
42 bottles of beer
|
||||
19
|
||||
|
@ -355,7 +355,7 @@ unicode strings have to be wrapped in their corresponding ``ctypes`` type, so
|
|||
that they can be converted to the required C data type::
|
||||
|
||||
>>> printf("An int %d, a double %f\n", 1234, c_double(3.14))
|
||||
Integer 1234, double 3.1400001049
|
||||
An int 1234, a double 3.140000
|
||||
31
|
||||
>>>
|
||||
|
||||
|
@ -411,9 +411,9 @@ prototype for a C function), and tries to convert the arguments to valid types::
|
|||
Traceback (most recent call last):
|
||||
File "<stdin>", line 1, in ?
|
||||
ArgumentError: argument 2: exceptions.TypeError: wrong type
|
||||
>>> printf("%s %d %f", "X", 2, 3)
|
||||
X 2 3.00000012
|
||||
12
|
||||
>>> printf("%s %d %f\n", "X", 2, 3)
|
||||
X 2 3.000000
|
||||
13
|
||||
>>>
|
||||
|
||||
If you have defined your own classes which you pass to function calls, you have
|
||||
|
|
|
@ -1072,10 +1072,10 @@ to a particular option, or fail to pass a required option attribute,
|
|||
tells :mod:`optparse` where to write it: :attr:`dest` names an attribute of the
|
||||
``options`` object that :mod:`optparse` builds as it parses the command line.
|
||||
|
||||
* ``default`` (deprecated)
|
||||
* ``default``
|
||||
|
||||
The value to use for this option's destination if the option is not seen on the
|
||||
command line. Deprecated; use ``parser.set_defaults()`` instead.
|
||||
command line. See also ``parser.set_defaults()``.
|
||||
|
||||
* ``nargs`` (default: 1)
|
||||
|
||||
|
|
|
@ -13,7 +13,7 @@ SQLite for internal data storage. It's also possible to prototype an
|
|||
application using SQLite and then port the code to a larger database such as
|
||||
PostgreSQL or Oracle.
|
||||
|
||||
pysqlite was written by Gerhard Häring and provides a SQL interface compliant
|
||||
sqlite3 was written by Gerhard Häring and provides a SQL interface compliant
|
||||
with the DB-API 2.0 specification described by :pep:`249`.
|
||||
|
||||
To use the module, you must first create a :class:`Connection` object that
|
||||
|
@ -50,8 +50,9 @@ is insecure; it makes your program vulnerable to an SQL injection attack.
|
|||
|
||||
Instead, use the DB-API's parameter substitution. Put ``?`` as a placeholder
|
||||
wherever you want to use a value, and then provide a tuple of values as the
|
||||
second argument to the cursor's :meth:`~Cursor.execute` method. (Other database modules
|
||||
may use a different placeholder, such as ``%s`` or ``:1``.) For example::
|
||||
second argument to the cursor's :meth:`~Cursor.execute` method. (Other database
|
||||
modules may use a different placeholder, such as ``%s`` or ``:1``.) For
|
||||
example::
|
||||
|
||||
# Never do this -- insecure!
|
||||
symbol = 'IBM'
|
||||
|
@ -90,11 +91,12 @@ This example uses the iterator form::
|
|||
.. seealso::
|
||||
|
||||
http://www.pysqlite.org
|
||||
The pysqlite web page.
|
||||
The pysqlite web page -- sqlite3 is developed externally under the name
|
||||
"pysqlite".
|
||||
|
||||
http://www.sqlite.org
|
||||
The SQLite web page; the documentation describes the syntax and the available
|
||||
data types for the supported SQL dialect.
|
||||
The SQLite web page; the documentation describes the syntax and the
|
||||
available data types for the supported SQL dialect.
|
||||
|
||||
:pep:`249` - Database API Specification 2.0
|
||||
PEP written by Marc-André Lemburg.
|
||||
|
@ -784,10 +786,10 @@ So if you are within a transaction and issue a command like ``CREATE TABLE
|
|||
...``, ``VACUUM``, ``PRAGMA``, the :mod:`sqlite3` module will commit implicitly
|
||||
before executing that command. There are two reasons for doing that. The first
|
||||
is that some of these commands don't work within transactions. The other reason
|
||||
is that pysqlite needs to keep track of the transaction state (if a transaction
|
||||
is that sqlite3 needs to keep track of the transaction state (if a transaction
|
||||
is active or not).
|
||||
|
||||
You can control which kind of ``BEGIN`` statements pysqlite implicitly executes
|
||||
You can control which kind of ``BEGIN`` statements sqlite3 implicitly executes
|
||||
(or none at all) via the *isolation_level* parameter to the :func:`connect`
|
||||
call, or via the :attr:`isolation_level` property of connections.
|
||||
|
||||
|
@ -799,8 +801,8 @@ statement, or set it to one of SQLite's supported isolation levels: "DEFERRED",
|
|||
|
||||
|
||||
|
||||
Using pysqlite efficiently
|
||||
--------------------------
|
||||
Using :mod:`sqlite3` efficiently
|
||||
--------------------------------
|
||||
|
||||
|
||||
Using shortcut methods
|
||||
|
|
|
@ -22,7 +22,7 @@ override the platform default list of browsers, as a os.pathsep-separated list
|
|||
of browsers to try in order. When the value of a list part contains the string
|
||||
``%s``, then it is interpreted as a literal browser command line to be used
|
||||
with the argument URL substituted for ``%s``; if the part does not contain
|
||||
``%s``, it is simply interpreted as the name of the browser to launch.
|
||||
``%s``, it is simply interpreted as the name of the browser to launch. [1]_
|
||||
|
||||
For non-Unix platforms, or when a remote browser is available on Unix, the
|
||||
controlling process will not wait for the user to finish with the browser, but
|
||||
|
@ -193,3 +193,9 @@ module-level convenience functions:
|
|||
|
||||
Open *url* in a new page ("tab") of the browser handled by this controller, if
|
||||
possible, otherwise equivalent to :func:`open_new`.
|
||||
|
||||
|
||||
.. rubric:: Footnotes
|
||||
|
||||
.. [1] Executables named here without a full path will be searched in the
|
||||
directories given in the :envvar:`PATH` environment variable.
|
||||
|
|
|
@ -28,7 +28,7 @@ DOM applications typically start by parsing some XML into a DOM. With
|
|||
The :func:`parse` function can take either a filename or an open file object.
|
||||
|
||||
|
||||
.. function:: parse(filename_or_file, parser)
|
||||
.. function:: parse(filename_or_file[, parser[, bufsize]])
|
||||
|
||||
Return a :class:`Document` from the given input. *filename_or_file* may be
|
||||
either a file name, or a file-like object. *parser*, if given, must be a SAX2
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue