# SOME DESCRIPTIVE TITLE.

# Copyright (C) 2001-2017, Python Software Foundation

# This file is distributed under the same license as the Python package.

# FIRST AUTHOR <EMAIL@ADDRESS>, 2017.

#

#, fuzzy

msgid ""

msgstr ""

"Project-Id-Version: Python 3.6\n"

"Report-Msgid-Bugs-To: \n"

"POT-Creation-Date: 2017-12-23 11:56+0900\n"

"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"

"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"

"Language-Team: LANGUAGE <LL@li.org>\n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=utf-8\n"

"Content-Transfer-Encoding: 8bit\n"

"Generated-By: Babel 2.5.1\n"

#: ../Doc/library/asyncio-eventloops.rst:4

msgid "Event loops"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:6

msgid "**Source code:** :source:`Lib/asyncio/events.py`"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:9

msgid "Event loop functions"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:11

msgid ""

"The following functions are convenient shortcuts to accessing the methods"

" of the global policy. Note that this provides access to the default "

"policy, unless an alternative policy was set by calling "

":func:`set_event_loop_policy` earlier in the execution of the process."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:18

msgid "Equivalent to calling ``get_event_loop_policy().get_event_loop()``."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:22

msgid "Equivalent to calling ``get_event_loop_policy().set_event_loop(loop)``."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:26

msgid "Equivalent to calling ``get_event_loop_policy().new_event_loop()``."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:32

msgid "Available event loops"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:34

msgid ""

"asyncio currently provides two implementations of event loops: "

":class:`SelectorEventLoop` and :class:`ProactorEventLoop`."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:39

msgid ""

"Event loop based on the :mod:`selectors` module. Subclass of "

":class:`AbstractEventLoop`."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:42

msgid "Use the most efficient selector available on the platform."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:44

msgid ""

"On Windows, only sockets are supported (ex: pipes are not supported): see"

" the `MSDN documentation of select <https://msdn.microsoft.com/en-"

"us/library/windows/desktop/ms740141%28v=vs.85%29.aspx>`_."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:50

msgid ""

"Proactor event loop for Windows using \"I/O Completion Ports\" aka IOCP. "

"Subclass of :class:`AbstractEventLoop`."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:53

msgid "Availability: Windows."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:57

msgid ""

"`MSDN documentation on I/O Completion Ports <https://msdn.microsoft.com"

"/en-us/library/windows/desktop/aa365198%28v=vs.85%29.aspx>`_."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:60

msgid "Example to use a :class:`ProactorEventLoop` on Windows::"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:71

msgid "Platform support"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:73

msgid ""

"The :mod:`asyncio` module has been designed to be portable, but each "

"platform still has subtle differences and may not support all "

":mod:`asyncio` features."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:77

msgid "Windows"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:79

msgid "Common limits of Windows event loops:"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:81

msgid ""

":meth:`~AbstractEventLoop.create_unix_connection` and "

":meth:`~AbstractEventLoop.create_unix_server` are not supported: the "

"socket family :data:`socket.AF_UNIX` is specific to UNIX"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:84

msgid ""

":meth:`~AbstractEventLoop.add_signal_handler` and "

":meth:`~AbstractEventLoop.remove_signal_handler` are not supported"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:86

msgid ""

":meth:`EventLoopPolicy.set_child_watcher` is not supported. "

":class:`ProactorEventLoop` supports subprocesses. It has only one "

"implementation to watch child processes, there is no need to configure "

"it."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:90

msgid ":class:`SelectorEventLoop` specific limits:"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:92

msgid ""

":class:`~selectors.SelectSelector` is used which only supports sockets "

"and is limited to 512 sockets."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:94

msgid ""

":meth:`~AbstractEventLoop.add_reader` and "

":meth:`~AbstractEventLoop.add_writer` only accept file descriptors of "

"sockets"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:96

msgid ""

"Pipes are not supported (ex: "

":meth:`~AbstractEventLoop.connect_read_pipe`, "

":meth:`~AbstractEventLoop.connect_write_pipe`)"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:99

msgid ""

":ref:`Subprocesses <asyncio-subprocess>` are not supported (ex: "

":meth:`~AbstractEventLoop.subprocess_exec`, "

":meth:`~AbstractEventLoop.subprocess_shell`)"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:103

msgid ":class:`ProactorEventLoop` specific limits:"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:105

msgid ":meth:`~AbstractEventLoop.create_datagram_endpoint` (UDP) is not supported"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:106

msgid ""

":meth:`~AbstractEventLoop.add_reader` and "

":meth:`~AbstractEventLoop.add_writer` are not supported"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:109

msgid ""

"The resolution of the monotonic clock on Windows is usually around 15.6 "

"msec. The best resolution is 0.5 msec. The resolution depends on the "

"hardware (availability of `HPET "

"<https://en.wikipedia.org/wiki/High_Precision_Event_Timer>`_) and on the "

"Windows configuration. See :ref:`asyncio delayed calls <asyncio-delayed-"

"calls>`."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:117

msgid ":class:`ProactorEventLoop` now supports SSL."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:121

msgid "Mac OS X"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:123

msgid ""

"Character devices like PTY are only well supported since Mavericks (Mac "

"OS 10.9). They are not supported at all on Mac OS 10.5 and older."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:126

msgid ""

"On Mac OS 10.6, 10.7 and 10.8, the default event loop is "

":class:`SelectorEventLoop` which uses :class:`selectors.KqueueSelector`. "

":class:`selectors.KqueueSelector` does not support character devices on "

"these versions. The :class:`SelectorEventLoop` can be used with "

":class:`~selectors.SelectSelector` or :class:`~selectors.PollSelector` to"

" support character devices on these versions of Mac OS X. Example::"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:142

msgid "Event loop policies and the default policy"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:144

msgid ""

"Event loop management is abstracted with a *policy* pattern, to provide "

"maximal flexibility for custom platforms and frameworks. Throughout the "

"execution of a process, a single global policy object manages the event "

"loops available to the process based on the calling context. A policy is "

"an object implementing the :class:`AbstractEventLoopPolicy` interface."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:150

msgid ""

"For most users of :mod:`asyncio`, policies never have to be dealt with "

"explicitly, since the default global policy is sufficient (see below)."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:153

msgid ""

"The module-level functions :func:`get_event_loop` and "

":func:`set_event_loop` provide convenient access to event loops managed "

"by the default policy."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:159

msgid "Event loop policy interface"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:161

msgid "An event loop policy must implement the following interface:"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:165

msgid "Event loop policy."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:169

msgid "Get the event loop for the current context."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:171

msgid ""

"Returns an event loop object implementing the :class:`AbstractEventLoop` "

"interface."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:174

msgid ""

"Raises an exception in case no event loop has been set for the current "

"context and the current policy does not specify to create one. It must "

"never return ``None``."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:180

msgid "Set the event loop for the current context to *loop*."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:184

msgid ""

"Create and return a new event loop object according to this policy's "

"rules."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:187

msgid ""

"If there's need to set this loop as the event loop for the current "

"context, :meth:`set_event_loop` must be called explicitly."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:191

msgid ""

"The default policy defines context as the current thread, and manages an "

"event loop per thread that interacts with :mod:`asyncio`. If the current"

" thread doesn't already have an event loop associated with it, the "

"default policy's :meth:`~AbstractEventLoopPolicy.get_event_loop` method "

"creates one when called from the main thread, but raises "

":exc:`RuntimeError` otherwise."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:199

msgid "Access to the global loop policy"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:203

msgid "Get the current event loop policy."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:207

msgid ""

"Set the current event loop policy. If *policy* is ``None``, the default "

"policy is restored."

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:212

msgid "Customizing the event loop policy"

msgstr ""

#: ../Doc/library/asyncio-eventloops.rst:214

msgid ""

"To implement a new event loop policy, it is recommended you subclass the "

"concrete default event loop policy :class:`DefaultEventLoopPolicy` and "

"override the methods for which you want to change behavior, for example::"

msgstr ""

#~ msgid ""

#~ "For most users of :mod:`asyncio`, "

#~ "policies never have to be dealt "

#~ "with explicitly, since the default "

#~ "global policy is sufficient."

#~ msgstr ""

#~ msgid ""

#~ "The default policy defines context as"

#~ " the current thread, and manages an"

#~ " event loop per thread that interacts"

#~ " with :mod:`asyncio`. The module-level "

#~ "functions :func:`get_event_loop` and "

#~ ":func:`set_event_loop` provide convenient access "

#~ "to event loops managed by the "

#~ "default policy."

#~ msgstr ""