Thanks to visit codestin.com
Credit goes to github.com

Skip to content

library/errors.po: 1 fuzzy #1876

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 20, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 6 additions & 10 deletions tutorial/errors.po
Original file line number Diff line number Diff line change
Expand Up @@ -6,14 +6,14 @@ msgstr ""
"Project-Id-Version: Python 3\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-03-18 17:06+0100\n"
"PO-Revision-Date: 2022-04-24 16:26+0200\n"
"PO-Revision-Date: 2022-05-20 09:47+0200\n"
"Last-Translator: Julien Palard <[email protected]>\n"
"Language-Team: FRENCH <[email protected]>\n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.4.2\n"
"X-Generator: Poedit 3.0.1\n"

#: tutorial/errors.rst:5
msgid "Errors and Exceptions"
Expand Down Expand Up @@ -418,21 +418,17 @@ msgstr ""
"classe :exc:`Exception`, directement ou non."

#: tutorial/errors.rst:330
#, fuzzy
msgid ""
"Exception classes can be defined which do anything any other class can do, "
"but are usually kept simple, often only offering a number of attributes that "
"allow information about the error to be extracted by handlers for the "
"exception."
msgstr ""
"Les classes d'exceptions peuvent être définies pour faire tout ce qu'une "
"autre classe peut faire. Elles sont le plus souvent gardées assez simples, "
"n'offrant que les attributs permettant aux gestionnaires de ces exceptions "
"d'extraire les informations relatives à l'erreur qui s'est produite. Lorsque "
"l'on crée un module qui peut déclencher plusieurs types d'erreurs distincts, "
"une pratique courante est de créer une classe de base pour l'ensemble des "
"exceptions définies dans ce module et de créer des sous-classes spécifiques "
"d'exceptions pour les différentes conditions d'erreurs ::"
"autre classe peut faire, mais elles sont le plus souvent gardées assez "
"simples, n'offrant que les attributs permettant aux gestionnaires de ces "
"exceptions d'extraire les informations relatives à l'erreur qui s'est "
"produite."

#: tutorial/errors.rst:334
msgid ""
Expand Down