# 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: 2025-10-11 20:40+0000\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.17.0\n"
#: ../../bugs.rst:5
msgid "Dealing with Bugs"
msgstr " "
#: ../../bugs.rst:7
msgid ""
"Python is a mature programming language which has established a "
"reputation for stability. In order to maintain this reputation, the "
"developers would like to know of any deficiencies you find in Python."
msgstr ""
" . , "
" ."
#: ../../bugs.rst:11
msgid ""
"It can be sometimes faster to fix bugs yourself and contribute patches to"
" Python as it streamlines the process and involves less people. Learn how"
" to :ref:`contribute `."
msgstr ""
" . "
":ref:` ` ."
#: ../../bugs.rst:16
msgid "Documentation bugs"
msgstr " "
#: ../../bugs.rst:18
#, fuzzy
msgid ""
"If you find a bug in this documentation or would like to propose an "
"improvement, please submit a bug report on the :ref:`issue tracker "
"`. If you have a suggestion on how to fix it, include"
" that as well."
msgstr ""
" , :ref:` ` "
" . , https://github.com/python/python-docs-"
"ko/issues . , ."
#: ../../bugs.rst:22
msgid ""
"You can also open a discussion item on our `Documentation Discourse forum"
" `_."
msgstr ""
#: ../../bugs.rst:25
msgid ""
"If you find a bug in the theme (HTML / CSS / JavaScript) of the "
"documentation, please submit a bug report on the `python-doc-theme issue "
"tracker `_."
msgstr ""
#: ../../bugs.rst:31
msgid "`Documentation bugs`_"
msgstr "` `_"
#: ../../bugs.rst:32
msgid ""
"A list of documentation bugs that have been submitted to the Python issue"
" tracker."
msgstr " ."
#: ../../bugs.rst:34
msgid "`Issue Tracking `_"
msgstr "` `_"
#: ../../bugs.rst:35
msgid ""
"Overview of the process involved in reporting an improvement on the "
"tracker."
msgstr " ."
#: ../../bugs.rst:37
msgid ""
"`Helping with Documentation `_"
msgstr ""
"` `_"
#: ../../bugs.rst:38
msgid ""
"Comprehensive guide for individuals that are interested in contributing "
"to Python documentation."
msgstr " ."
#: ../../bugs.rst:40
msgid ""
"`Documentation Translations "
"`_"
msgstr "` `_"
#: ../../bugs.rst:41
msgid ""
"A list of GitHub pages for documentation translation and their primary "
"contacts."
msgstr ""
#: ../../bugs.rst:47
msgid "Using the Python issue tracker"
msgstr " "
#: ../../bugs.rst:49
msgid ""
"Issue reports for Python itself should be submitted via the GitHub issues"
" tracker (https://github.com/python/cpython/issues). The GitHub issues "
"tracker offers a web form which allows pertinent information to be "
"entered and submitted to the developers."
msgstr ""
" GitHub (https://github.com/python/cpython/issues) "
" . GitHub ."
#: ../../bugs.rst:54
msgid ""
"The first step in filing a report is to determine whether the problem has"
" already been reported. The advantage in doing so, aside from saving the"
" developers' time, is that you learn what has been done to fix it; it may"
" be that the problem has already been fixed for the next release, or "
"additional information is needed (in which case you are welcome to "
"provide it if you can!). To do this, search the tracker using the search "
"box at the top of the page."
msgstr ""
" . , "
" . , "
" ( !). , "
" ."
#: ../../bugs.rst:61
msgid ""
"If the problem you're reporting is not already in the list, log in to "
"GitHub. If you don't already have a GitHub account, create a new account "
"using the \"Sign up\" link. It is not possible to submit a bug report "
"anonymously."
msgstr ""
" , GitHub . GitHub , \"Sign up\" "
" . ."
#: ../../bugs.rst:66
msgid ""
"Being now logged in, you can submit an issue. Click on the \"New issue\" "
"button in the top bar to report a new issue."
msgstr " , . \"New issue\" ."
#: ../../bugs.rst:69
msgid "The submission form has two fields, \"Title\" and \"Comment\"."
msgstr ""
#: ../../bugs.rst:71
msgid ""
"For the \"Title\" field, enter a *very* short description of the problem;"
" fewer than ten words is good."
msgstr ""
#: ../../bugs.rst:74
msgid ""
"In the \"Comment\" field, describe the problem in detail, including what "
"you expected to happen and what did happen. Be sure to include whether "
"any extension modules were involved, and what hardware and software "
"platform you were using (including version information as appropriate)."
msgstr ""
"\"Comment\" , , . "
", ( ) ."
#: ../../bugs.rst:79
msgid ""
"Each issue report will be reviewed by a developer who will determine what"
" needs to be done to correct the problem. You will receive an update each"
" time an action is taken on the issue."
msgstr ""
" . "
" ."
#: ../../bugs.rst:86
msgid ""
"`How to Report Bugs Effectively "
"`_"
msgstr ""
"` "
"`_"
#: ../../bugs.rst:87
msgid ""
"Article which goes into some detail about how to create a useful bug "
"report. This describes what kind of information is useful and why it is "
"useful."
msgstr " . ."
#: ../../bugs.rst:90
msgid ""
"`Bug Writing Guidelines `_"
msgstr "` `_"
#: ../../bugs.rst:91
msgid ""
"Information about writing a good bug report. Some of this is specific to"
" the Mozilla project, but describes general good practices."
msgstr " . (Mozilla) , ."
#: ../../bugs.rst:97
msgid "Getting started contributing to Python yourself"
msgstr " "
#: ../../bugs.rst:99
msgid ""
"Beyond just reporting bugs that you find, you are also welcome to submit "
"patches to fix them. You can find more information on how to get started"
" patching Python in the `Python Developer's Guide`_. If you have "
"questions, the `core-mentorship mailing list`_ is a friendly place to get"
" answers to any and all questions pertaining to the process of fixing "
"issues in Python."
msgstr ""
" , . "
"`Python Developer's Guide`_ . , `core-mentorship "
"mailing list`_ ."
#~ msgid ""
#~ "The submission form has a number "
#~ "of fields. For the \"Title\" field, "
#~ "enter a *very* short description of "
#~ "the problem; less than ten words "
#~ "is good. In the \"Type\" field, "
#~ "select the type of your problem; "
#~ "also select the \"Component\" and "
#~ "\"Versions\" to which the bug relates."
#~ msgstr ""
#~ " . \"Title\" "
#~ " ** ; 10"
#~ " . \"Type\" "
#~ "; \"Component\" "
#~ "\"Versions\" ."
#~ msgid ""
#~ "If you find a bug in the "
#~ "theme (HTML / CSS / JavaScript) of"
#~ " the documentation, please submit a "
#~ "bug report on the `python-doc-"
#~ "theme bug tracker `_."
#~ msgstr ""
#~ msgid ""
#~ "If you're short on time, you can"
#~ " also email documentation bug reports "
#~ "to docs@python.org (behavioral bugs can "
#~ "be sent to python-list@python.org). "
#~ "'docs@' is a mailing list run by"
#~ " volunteers; your request will be "
#~ "noticed, though it may take a "
#~ "while to be processed."
#~ msgstr ""
#~ " , docs@python.org"
#~ " ( "
#~ " python-list@python.org "
#~ "). 'docs@' "
#~ "; "
#~ ", ."