[ Web Proxy ]
URL:
Viewing: https://raw.githubusercontent.com/python/python-docs-ko/3.9/library/asyncio-dev.po [Back]  [Original]

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2017, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR , 2017.
#
msgid ""
msgstr ""
"Project-Id-Version: Python 3.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-10-08 03:37+0900\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Dong-gweon Oh \n"
"Language-Team: Korean (https://python.flowdas.com)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:7
msgid "Developing with asyncio"
msgstr "asyncio "

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:9
msgid ""
"Asynchronous programming is different from classic \"sequential\" "
"programming."
msgstr "   \"\"  ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:12
msgid "This page lists common mistakes and traps and explains how to avoid them."
msgstr "     ,    ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:19
msgid "Debug Mode"
msgstr " "

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:21
msgid ""
"By default asyncio runs in production mode.  In order to ease the "
"development asyncio has a *debug mode*."
msgstr " asyncio   .    asyncio * *\\ ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:24
msgid "There are several ways to enable asyncio debug mode:"
msgstr "   asyncio     :"

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:26
msgid "Setting the :envvar:`PYTHONASYNCIODEBUG` environment variable to ``1``."
msgstr ":envvar:`PYTHONASYNCIODEBUG`   ``1``\\ ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:28
msgid "Using the :ref:`Python Development Mode `."
msgstr ":ref:`   ` ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:30
msgid "Passing ``debug=True`` to :func:`asyncio.run`."
msgstr "``debug=True``\\ :func:`asyncio.run`\\ ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:32
msgid "Calling :meth:`loop.set_debug`."
msgstr ":meth:`loop.set_debug`\\ ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:34
msgid "In addition to enabling the debug mode, consider also:"
msgstr "    ,  :"

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:36
msgid ""
"setting the log level of the :ref:`asyncio logger ` to "
":py:data:`logging.DEBUG`, for example the following snippet of code can "
"be run at startup of the application::"
msgstr ""
":ref:`asyncio  `\\   :py:data:`logging.DEBUG`\\ "
",            ::"

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:42
msgid ""
"configuring the :mod:`warnings` module to display :exc:`ResourceWarning` "
"warnings.  One way of doing that is by using the :option:`-W` ``default``"
" command line option."
msgstr ""
":exc:`ResourceWarning`   :mod:`warnings`  .      "
":option:`-W` ``default``     ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:47
msgid "When the debug mode is enabled:"
msgstr "  :"

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:49
msgid ""
"asyncio checks for :ref:`coroutines that were not awaited ` and logs them; this mitigates the \"forgotten "
"await\" pitfall."
msgstr ""
"asyncio :ref:`   `\\   "
";  \" await\"  ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:53
msgid ""
"Many non-threadsafe asyncio APIs (such as :meth:`loop.call_soon` and "
":meth:`loop.call_at` methods) raise an exception if they are called from "
"a wrong thread."
msgstr ""
"    asyncio API(:meth:`loop.call_soon`\\ :meth:`loop.call_at`"
"  )      ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:57
msgid ""
"The execution time of the I/O selector is logged if it takes too long to "
"perform an I/O operation."
msgstr "I/O    I/O       ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:60
msgid ""
"Callbacks taking longer than 100ms are logged.  The "
":attr:`loop.slow_callback_duration` attribute can be used to set the "
"minimum execution duration in seconds that is considered \"slow\"."
msgstr ""
"100ms     . :attr:`loop.slow_callback_duration`  "
"\"\"     ()     ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:68
msgid "Concurrency and Multithreading"
msgstr "  "

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:70
msgid ""
"An event loop runs in a thread (typically the main thread) and executes "
"all callbacks and Tasks in its thread.  While a Task is running in the "
"event loop, no other Tasks can run in the same thread.  When a Task "
"executes an ``await`` expression, the running Task gets suspended, and "
"the event loop executes the next Task."
msgstr ""
"  (  )       .    "
" ,       .  ``await``  ,   "
"       ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:76
msgid ""
"To schedule a :term:`callback` from another OS thread, the "
":meth:`loop.call_soon_threadsafe` method should be used. Example::"
msgstr ""
" OS  :term:` `\\ , "
":meth:`loop.call_soon_threadsafe`   . ::"

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:81
msgid ""
"Almost all asyncio objects are not thread safe, which is typically not a "
"problem unless there is code that works with them from outside of a Task "
"or a callback.  If there's a need for such code to call a low-level "
"asyncio API, the :meth:`loop.call_soon_threadsafe` method should be used,"
" e.g.::"
msgstr ""
"  asyncio    .          "
".    asyncio API  , :meth:`loop.call_soon_threadsafe`"
"   ,  ::"

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:89
msgid ""
"To schedule a coroutine object from a different OS thread, the "
":func:`run_coroutine_threadsafe` function should be used. It returns a "
":class:`concurrent.futures.Future` to access the result::"
msgstr ""
" OS    , :func:`run_coroutine_threadsafe`   ."
"     :class:`concurrent.futures.Future`\\ ::"

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:102
msgid ""
"To handle signals and to execute subprocesses, the event loop must be run"
" in the main thread."
msgstr "    ,      ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:105
msgid ""
"The :meth:`loop.run_in_executor` method can be used with a "
":class:`concurrent.futures.ThreadPoolExecutor` to execute blocking code "
"in a different OS thread without blocking the OS thread that the event "
"loop runs in."
msgstr ""
":meth:`loop.run_in_executor`  "
":class:`concurrent.futures.ThreadPoolExecutor`\\  ,    "
"OS     OS      ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:110
msgid ""
"There is currently no way to schedule coroutines or callbacks directly "
"from a different process (such as one started with "
":mod:`multiprocessing`). The :ref:`Event Loop Methods ` section lists APIs that can read from pipes and watch file "
"descriptors without blocking the event loop. In addition, asyncio's "
":ref:`Subprocess ` APIs provide a way to start a "
"process and communicate with it from the event loop. Lastly, the "
"aforementioned :meth:`loop.run_in_executor` method can also be used with "
"a :class:`concurrent.futures.ProcessPoolExecutor` to execute code in a "
"different process."
msgstr ""
"  ( :mod:`multiprocessing`\\  )     "
" . :ref:`   `       "
"      API .  asyncio :ref:`  ` API        . ,  "
" :meth:`loop.run_in_executor`  "
":class:`concurrent.futures.ProcessPoolExecutor`\\      "
"  ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:124
msgid "Running Blocking Code"
msgstr "  "

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:126
msgid ""
"Blocking (CPU-bound) code should not be called directly.  For example, if"
" a function performs a CPU-intensive calculation for 1 second, all "
"concurrent asyncio Tasks and IO operations would be delayed by 1 second."
msgstr ""
" (CPU )     .  ,  CPU   1  ,  "
" asyncio  IO  1 ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:131
msgid ""
"An executor can be used to run a task in a different thread or even in a "
"different process to avoid blocking the OS thread with the event loop.  "
"See the :meth:`loop.run_in_executor` method for more details."
msgstr ""
" ,     OS   ,       "
"  .   :meth:`loop.run_in_executor`  ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:140
msgid "Logging"
msgstr ""

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:142
msgid ""
"asyncio uses the :mod:`logging` module and all logging is performed via "
"the ``\"asyncio\"`` logger."
msgstr "asyncio :mod:`logging`  ,   ``\"asyncio\"``   ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:145
msgid ""
"The default log level is :py:data:`logging.INFO`, which can be easily "
"adjusted::"
msgstr "   :py:data:`logging.INFO`\\,    ::"

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:154
msgid "Detect never-awaited coroutines"
msgstr "await    "

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:156
msgid ""
"When a coroutine function is called, but not awaited (e.g. ``coro()`` "
"instead of ``await coro()``) or the coroutine is not scheduled with "
":meth:`asyncio.create_task`, asyncio will emit a :exc:`RuntimeWarning`::"
msgstr ""
"     ( , ``await coro()``  ``coro()``)  "
":meth:`asyncio.create_task`\\   asyncio :exc:`RuntimeWarning`\\"
" ::"

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:171
#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:216
msgid "Output::"
msgstr "::"

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:176
#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:232
msgid "Output in debug mode::"
msgstr "  ::"

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:189
msgid ""
"The usual fix is to either await the coroutine or call the "
":meth:`asyncio.create_task` function::"
msgstr "   await  :meth:`asyncio.create_task`   ::"

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:197
msgid "Detect never-retrieved exceptions"
msgstr "   "

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:199
msgid ""
"If a :meth:`Future.set_exception` is called but the Future object is "
"never awaited on, the exception would never be propagated to the user "
"code.  In this case, asyncio would emit a log message when the Future "
"object is garbage collected."
msgstr ""
":meth:`Future.set_exception`\\ , Future  await  ,   "
"   .  , Future     asyncio   ."

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:204
msgid "Example of an unhandled exception::"
msgstr "   ::"

#: /Users/flowdas/works/docs/python-docs-ko/src/Doc/library/asyncio-dev.rst:227
msgid ""
":ref:`Enable the debug mode ` to get the traceback "
"where the task was created::"
msgstr "     :ref:`   `::"


Web Proxy Viewer  |  New URL  |  Original Page