pytho****@googl*****
pytho****@googl*****
2011年 12月 5日 (月) 22:31:41 JST
2 new revisions: Revision: d74112455c96 Author: Akihiro Uchida <uchid****@ike-d*****> Date: Mon Dec 5 05:29:48 2011 Log: fix c markups http://code.google.com/p/python-doc-ja/source/detail?r=d74112455c96 Revision: 338623991819 Author: Akihiro Uchida <uchid****@ike-d*****> Date: Mon Dec 5 05:30:58 2011 Log: role 前後の空白もれなどを修正 http://code.google.com/p/python-doc-ja/source/detail?r=338623991819 ============================================================================== Revision: d74112455c96 Author: Akihiro Uchida <uchid****@ike-d*****> Date: Mon Dec 5 05:29:48 2011 Log: fix c markups http://code.google.com/p/python-doc-ja/source/detail?r=d74112455c96 Modified: /whatsnew/2.4.rst ======================================= --- /whatsnew/2.4.rst Sun Dec 4 07:39:56 2011 +++ /whatsnew/2.4.rst Mon Dec 5 05:29:48 2011 @@ -498,7 +498,7 @@ 5. Modern systems usually provide floating-point support that conforms to a -standard called IEEE 754. C's :ctype:`double` type is usually implemented as a +standard called IEEE 754. C's :c:type:`double` type is usually implemented as a 64-bit IEEE 754 number, which uses 52 bits of space for the mantissa. This means that numbers can only be specified to 52 bits of precision. If you're trying to represent numbers whose expansion repeats endlessly, the expansion is @@ -736,7 +736,7 @@ However, the module was careful to not change the numeric locale because various functions in Python's implementation required that the numeric locale remain set to the ``'C'`` locale. Often this was because the code was using the C -library's :cfunc:`atof` function. +library's :c:func:`atof` function. Not setting the numeric locale caused trouble for extensions that used third- party C libraries, however, because they wouldn't have the correct locale set. @@ -746,11 +746,11 @@ The solution described in the PEP is to add three new functions to the Python API that perform ASCII-only conversions, ignoring the locale setting: -* :cfunc:`PyOS_ascii_strtod(str, ptr)` and :cfunc:`PyOS_ascii_atof(str, ptr)` - both convert a string to a C :ctype:`double`. - -* :cfunc:`PyOS_ascii_formatd(buffer, buf_len, format, d)` converts a - :ctype:`double` to an ASCII string. +* :c:func:`PyOS_ascii_strtod(str, ptr)` and :c:func:`PyOS_ascii_atof(str, ptr)` + both convert a string to a C :c:type:`double`. + +* :c:func:`PyOS_ascii_formatd(buffer, buf_len, format, d)` converts a + :c:type:`double` to an ASCII string. The code for these functions came from the GLib library (http://library.gnome.org/devel/glib/stable/), whose developers kindly @@ -938,7 +938,7 @@ * The machinery for growing and shrinking lists was optimized for speed and for space efficiency. Appending and popping from lists now runs faster due to more efficient code paths and less frequent use of the underlying system - :cfunc:`realloc`. List comprehensions also benefit. :meth:`list.extend` was + :c:func:`realloc`. List comprehensions also benefit. :meth:`list.extend` was also optimized and no longer converts its argument into a temporary list before extending the base list. (Contributed by Raymond Hettinger.) @@ -1445,34 +1445,34 @@ Some of the changes to Python's build process and to the C API are: * Three new convenience macros were added for common return values from - extension functions: :cmacro:`Py_RETURN_NONE`, :cmacro:`Py_RETURN_TRUE`, and - :cmacro:`Py_RETURN_FALSE`. (Contributed by Brett Cannon.) - -* Another new macro, :cmacro:`Py_CLEAR(obj)`, decreases the reference count of + extension functions: :c:macro:`Py_RETURN_NONE`, :c:macro:`Py_RETURN_TRUE`, and + :c:macro:`Py_RETURN_FALSE`. (Contributed by Brett Cannon.) + +* Another new macro, :c:macro:`Py_CLEAR(obj)`, decreases the reference count of *obj* and sets *obj* to the null pointer. (Contributed by Jim Fulton.) -* A new function, :cfunc:`PyTuple_Pack(N, obj1, obj2, ..., objN)`, constructs +* A new function, :c:func:`PyTuple_Pack(N, obj1, obj2, ..., objN)`, constructs tuples from a variable length argument list of Python objects. (Contributed by Raymond Hettinger.) -* A new function, :cfunc:`PyDict_Contains(d, k)`, implements fast dictionary +* A new function, :c:func:`PyDict_Contains(d, k)`, implements fast dictionary lookups without masking exceptions raised during the look-up process. (Contributed by Raymond Hettinger.) -* The :cmacro:`Py_IS_NAN(X)` macro returns 1 if its float or double argument +* The :c:macro:`Py_IS_NAN(X)` macro returns 1 if its float or double argument *X* is a NaN. (Contributed by Tim Peters.) * C code can avoid unnecessary locking by using the new - :cfunc:`PyEval_ThreadsInitialized` function to tell if any thread operations + :c:func:`PyEval_ThreadsInitialized` function to tell if any thread operations have been performed. If this function returns false, no lock operations are needed. (Contributed by Nick Coghlan.) -* A new function, :cfunc:`PyArg_VaParseTupleAndKeywords`, is the same as - :cfunc:`PyArg_ParseTupleAndKeywords` but takes a :ctype:`va_list` instead of a +* A new function, :c:func:`PyArg_VaParseTupleAndKeywords`, is the same as + :c:func:`PyArg_ParseTupleAndKeywords` but takes a :c:type:`va_list` instead of a number of arguments. (Contributed by Greg Chapman.) * A new method flag, :const:`METH_COEXISTS`, allows a function defined in slots - to co-exist with a :ctype:`PyCFunction` having the same name. This can halve + to co-exist with a :c:type:`PyCFunction` having the same name. This can halve the access time for a method such as :meth:`set.__contains__`. (Contributed by Raymond Hettinger.) @@ -1486,8 +1486,8 @@ though that processor architecture doesn't call that register "the TSC register". (Contributed by Jeremy Hylton.) -* The :ctype:`tracebackobject` type has been renamed to - :ctype:`PyTracebackObject`. +* The :c:type:`tracebackobject` type has been renamed to + :c:type:`PyTracebackObject`. .. ====================================================================== ============================================================================== Revision: 338623991819 Author: Akihiro Uchida <uchid****@ike-d*****> Date: Mon Dec 5 05:30:58 2011 Log: role 前後の空白もれなどを修正 http://code.google.com/p/python-doc-ja/source/detail?r=338623991819 Modified: /library/functions.rst /library/logging.rst /library/stdtypes.rst ======================================= --- /library/functions.rst Thu Dec 1 06:50:52 2011 +++ /library/functions.rst Mon Dec 5 05:30:58 2011 @@ -1220,7 +1220,7 @@ .. note:: 浮動小数点数に対する :func:`round` の振る舞いは意外なものかもしれませ ん: - 例えば、``round(2.675, 2)'' は予想通りの ``2.68`` ではなく + 例えば、 ``round(2.675, 2)'' は予想通りの ``2.68`` ではなく ``2.67`` を与えます。これはバグではありません: これはほとんどの 少数が浮動小数点数で正確に表せないことの結果です。詳しくは :ref:`tut-fp-issues` を参照してください。 ======================================= --- /library/logging.rst Fri Dec 2 08:08:19 2011 +++ /library/logging.rst Mon Dec 5 05:30:58 2011 @@ -744,8 +744,6 @@ .. function:: log(level, msg[, *args[, **kwargs]]) - Logs a message with level *level* on the root logger. The other arguments are - interpreted as for :func:`debug`. レベル *level* のメッセージをルートロガーで記録します。 その他の引数は :func:`debug` と同じように解釈されます。 ======================================= --- /library/stdtypes.rst Thu Dec 1 06:50:52 2011 +++ /library/stdtypes.rst Mon Dec 5 05:30:58 2011 @@ -2427,7 +2427,7 @@ ファイルから一行全部を読み込みます。終末の改行文字は文字列に残ります (しかし、ファイルが不完全な行で終わっていたら、存在しないかもしれません )。 [#]_ *size* 引数が与えられ、負でなければ、それが (終末の改行文字を含む) - 最大バイト数となり、不完全な行でも返されます。*size* が 0 でなければ、 + 最大バイト数となり、不完全な行でも返されます。 *size* が 0 でなければ、 空の文字列が返されるのは、即座に EOF に到達したとき *だけ* です。 @@ -2620,7 +2620,7 @@ *obj* を参照する :class:`memoryview` を作成します。*obj* は バッファプロトコルをサポートしていなければなりません。 バッファプロトコルをサポートする組み込みオブジェクトには、 - :class:`str` 、:class:`bytearray` などがあります + :class:`str` 、 :class:`bytearray` などがあります (ただし、 :class:`unicode` は違います)。 :class:`memoryview` には *要素* の概念があり、それが起源のオブジェクト
