# SOME DESCRIPTIVE TITLE. # Copyright (C) 2001-2016, Python Software Foundation # This file is distributed under the same license as the Python package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Python 3.6\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2016-10-17 21:44+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../Doc/bugs.rst:5 msgid "Dealing with Bugs" msgstr "" #: ../Doc/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 "" #: ../Doc/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 "" #: ../Doc/bugs.rst:16 msgid "Documentation bugs" msgstr "" #: ../Doc/bugs.rst:18 msgid "" "If you find a bug in this documentation or would like to propose an " "improvement, please submit a bug report on the :ref:`tracker `. If you have a suggestion how to fix it, include that as well." msgstr "" #: ../Doc/bugs.rst:22 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 "" #: ../Doc/bugs.rst:28 msgid "`Documentation bugs`_ on the Python issue tracker" msgstr "" #: ../Doc/bugs.rst:33 msgid "Using the Python issue tracker" msgstr "" #: ../Doc/bugs.rst:35 msgid "" "Bug reports for Python itself should be submitted via the Python Bug Tracker " "(https://bugs.python.org/). The bug tracker offers a Web form which allows " "pertinent information to be entered and submitted to the developers." msgstr "" #: ../Doc/bugs.rst:39 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 bug database using the search box on the top " "of the page." msgstr "" #: ../Doc/bugs.rst:46 msgid "" "If the problem you're reporting is not already in the bug tracker, go back " "to the Python Bug Tracker and log in. If you don't already have a tracker " "account, select the \"Register\" link or, if you use OpenID, one of the " "OpenID provider logos in the sidebar. It is not possible to submit a bug " "report anonymously." msgstr "" #: ../Doc/bugs.rst:51 msgid "" "Being now logged in, you can submit a bug. Select the \"Create New\" link " "in the sidebar to open the bug reporting form." msgstr "" #: ../Doc/bugs.rst:54 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 "" #: ../Doc/bugs.rst:59 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 "" #: ../Doc/bugs.rst:64 msgid "" "Each bug report will be assigned to a developer who will determine what " "needs to be done to correct the problem. You will receive an update each " "time action is taken on the bug." msgstr "" #: ../Doc/bugs.rst:73 msgid "" "`How to Report Bugs Effectively `_" msgstr "" #: ../Doc/bugs.rst:72 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 "" #: ../Doc/bugs.rst:76 msgid "" "`Bug Writing Guidelines `_" msgstr "" #: ../Doc/bugs.rst:76 msgid "" "Information about writing a good bug report. Some of this is specific to " "the Mozilla project, but describes general good practices." msgstr "" #: ../Doc/bugs.rst:82 msgid "Getting started contributing to Python yourself" msgstr "" #: ../Doc/bugs.rst:84 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 ""