}
.. note::
+
There are limitations to what you can safely do in a deallocator function.
First, if your type supports garbage collection (using :c:member:`~PyTypeObject.tp_traverse`
and/or :c:member:`~PyTypeObject.tp_clear`), some of the object's members can have been
:c:member:`~PyTypeObject.tp_finalize` type method.
.. seealso::
+
:pep:`442` explains the new finalization scheme.
.. index::
>>> urllib.parse.urlencode({'name': 'Guy Steele, Jr.'})
'name=Guy+Steele%2C+Jr.'
-.. seealso:: :ref:`urllib-howto` for extensive examples.
+.. seealso::
+
+ :ref:`urllib-howto` for extensive examples.
What module should I use to help with generating HTML?
(Namespace(bar='BAR', foo=True), ['--badger', 'spam'])
.. warning::
+
:ref:`Prefix matching <prefix-matching>` rules apply to
:meth:`parse_known_args`. The parser may consume an option even if it's just
a prefix of one of its known options, instead of leaving it in the remaining
the transport; if *ssl* is :const:`True`, a context with some
unspecified default settings is used.
- .. seealso:: :ref:`SSL/TLS security considerations <ssl-security>`
+ .. seealso::
+
+ :ref:`SSL/TLS security considerations <ssl-security>`
* *server_hostname*, is only for use together with *ssl*,
and sets or overrides the hostname that the target server's certificate
buffer size reaches the low-water mark.
.. note::
+
If the buffer size equals the high-water mark,
:meth:`pause_writing` is not called -- it must go strictly over.
Conversely, :meth:`resume_writing` is called when the buffer size is
mark is zero.
.. note::
+
On BSD systems (OS X, FreeBSD, etc.) flow control is not supported
for :class:`DatagramProtocol`, because send failures caused by
writing too many packets cannot be detected easily. The socket
the future.
.. note::
+
The :meth:`~BaseEventLoop.run_until_complete` method uses internally the
:meth:`~Future.add_done_callback` method to be notified when the future is
done.
``message/rfc822``, use ``8bit`` if *cte* is not specified. For all
other values of *subtype*, use ``7bit``.
- .. note:: A *cte* of ``binary`` does not actually work correctly yet.
+ .. note::
+
+ A *cte* of ``binary`` does not actually work correctly yet.
The ``Message`` object as modified by ``set_content`` is correct, but
:class:`~email.generator.BytesGenerator` does not serialize it
correctly.
:meth:`mapLogRecord` method is used to convert the record to the
dictionary to be sent.
- .. note:: Since preparing a record for sending it to a Web server is not
+ .. note::
+
+ Since preparing a record for sending it to a Web server is not
the same as a generic formatting operation, using
:meth:`~logging.Handler.setFormatter` to specify a
:class:`~logging.Formatter` for a :class:`HTTPHandler` has no effect.
:exc:`NotImplementedError`.
.. seealso::
+
:func:`os.cpu_count`
.. function:: current_process()
``'ce'``, ``'java'``.
.. seealso::
+
:attr:`sys.platform` has a finer granularity. :func:`os.uname` gives
system-dependent version information.
useful since those simply don't have any OS-accessing operations.
.. note::
+
This module has been included in the standard library on a
:term:`provisional basis <provisional package>`. Backwards incompatible
changes (up to and including removal of the package) may occur if deemed
necessary by the core developers.
.. seealso::
+
:pep:`428`: The pathlib module -- object-oriented filesystem paths.
.. seealso::
+
For low-level path manipulation on strings, you can also use the
:mod:`os.path` module.
brought by protocol 4.
.. note::
+
Serialization is a more primitive notion than persistence; although
:mod:`pickle` reads and writes file objects, it does not handle the issue of
naming persistent objects, nor the (even more complicated) issue of concurrent
default CA certificates.
.. note::
+
The protocol, options, cipher and other settings may change to more
restrictive values anytime without prior deprecation. The values
represent a fair balance between compatibility and security.
:class:`SSLContext` and apply the settings yourself.
.. note::
+
If you find that when certain older clients or servers attempt to connect
with a :class:`SSLContext` created by this function that they get an
error stating "Protocol or cipher suite mismatch", it may be that they
interoperability.
.. seealso::
+
:func:`create_default_context` lets the :mod:`ssl` module choose
security settings for a given purpose.
This is suited for when your data is discrete, and you don't mind that the
median may not be an actual data point.
- .. seealso:: :func:`median_low`, :func:`median_high`, :func:`median_grouped`
+ .. seealso::
+
+ :func:`median_low`, :func:`median_high`, :func:`median_grouped`
.. function:: median_low(data)
:ref:`documentation of view objects <dict-views>`.
.. seealso::
+
:class:`types.MappingProxyType` can be used to create a read-only view
of a :class:`dict`.
.. seealso::
+
Module :mod:`site` This describes how to use .pth files to extend
:data:`sys.path`.
custom implementations.
.. seealso::
+
:func:`logging.captureWarnings` allows you to handle all warnings with
the standard logging infrastructure.
python -mtimeit -h # for details
.. seealso::
+
:func:`runpy.run_module`
Equivalent functionality directly available to Python code
.. versionchanged:: 3.4
Automatic enabling of tab-completion and history editing.
-.. seealso:: :ref:`tut-invoking`
+.. seealso::
+
+ :ref:`tut-invoking`
Generic options
thus equivalent to an omitted line number.
.. seealso::
+
:mod:`warnings` -- the warnings module
:pep:`230` -- Warning framework