# 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: 2017-04-02 22:11+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "Language: fr\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../Doc/library/email.errors.rst:2 msgid ":mod:`email.errors`: Exception and Defect classes" msgstr "" #: ../Doc/library/email.errors.rst:7 msgid "**Source code:** :source:`Lib/email/errors.py`" msgstr "" #: ../Doc/library/email.errors.rst:11 msgid "" "The following exception classes are defined in the :mod:`email.errors` " "module:" msgstr "" #: ../Doc/library/email.errors.rst:16 msgid "" "This is the base class for all exceptions that the :mod:`email` package can " "raise. It is derived from the standard :exc:`Exception` class and defines " "no additional methods." msgstr "" #: ../Doc/library/email.errors.rst:23 msgid "" "This is the base class for exceptions raised by the :class:`~email.parser." "Parser` class. It is derived from :exc:`MessageError`. This class is also " "used internally by the parser used by :mod:`~email.headerregistry`." msgstr "" #: ../Doc/library/email.errors.rst:31 msgid "" "Raised under some error conditions when parsing the :rfc:`5322` headers of a " "message, this class is derived from :exc:`MessageParseError`. The :meth:" "`~email.message.EmailMessage.set_boundary` method will raise this error if " "the content type is unknown when the method is called. :class:`~email.header." "Header` may raise this error for certain base64 decoding errors, and when an " "attempt is made to create a header that appears to contain an embedded " "header (that is, there is what is supposed to be a continuation line that " "has no leading whitespace and looks like a header)." msgstr "" #: ../Doc/library/email.errors.rst:43 msgid "Deprecated and no longer used." msgstr "" #: ../Doc/library/email.errors.rst:48 msgid "" "Raised when a payload is added to a :class:`~email.message.Message` object " "using :meth:`add_payload`, but the payload is already a scalar and the " "message's :mailheader:`Content-Type` main type is not either :mimetype:" "`multipart` or missing. :exc:`MultipartConversionError` multiply inherits " "from :exc:`MessageError` and the built-in :exc:`TypeError`." msgstr "" #: ../Doc/library/email.errors.rst:54 msgid "" "Since :meth:`Message.add_payload` is deprecated, this exception is rarely " "raised in practice. However the exception may also be raised if the :meth:" "`~email.message.Message.attach` method is called on an instance of a class " "derived from :class:`~email.mime.nonmultipart.MIMENonMultipart` (e.g. :class:" "`~email.mime.image.MIMEImage`)." msgstr "" #: ../Doc/library/email.errors.rst:62 msgid "" "Here is the list of the defects that the :class:`~email.parser.FeedParser` " "can find while parsing messages. Note that the defects are added to the " "message where the problem was found, so for example, if a message nested " "inside a :mimetype:`multipart/alternative` had a malformed header, that " "nested message object would have a defect, but the containing messages would " "not." msgstr "" #: ../Doc/library/email.errors.rst:68 msgid "" "All defect classes are subclassed from :class:`email.errors.MessageDefect`." msgstr "" #: ../Doc/library/email.errors.rst:70 msgid "" ":class:`NoBoundaryInMultipartDefect` -- A message claimed to be a multipart, " "but had no :mimetype:`boundary` parameter." msgstr "" #: ../Doc/library/email.errors.rst:73 msgid "" ":class:`StartBoundaryNotFoundDefect` -- The start boundary claimed in the :" "mailheader:`Content-Type` header was never found." msgstr "" #: ../Doc/library/email.errors.rst:76 msgid "" ":class:`CloseBoundaryNotFoundDefect` -- A start boundary was found, but no " "corresponding close boundary was ever found." msgstr "" #: ../Doc/library/email.errors.rst:81 msgid "" ":class:`FirstHeaderLineIsContinuationDefect` -- The message had a " "continuation line as its first header line." msgstr "" #: ../Doc/library/email.errors.rst:84 msgid "" ":class:`MisplacedEnvelopeHeaderDefect` - A \"Unix From\" header was found in " "the middle of a header block." msgstr "" #: ../Doc/library/email.errors.rst:87 msgid "" ":class:`MissingHeaderBodySeparatorDefect` - A line was found while parsing " "headers that had no leading white space but contained no ':'. Parsing " "continues assuming that the line represents the first line of the body." msgstr "" #: ../Doc/library/email.errors.rst:93 msgid "" ":class:`MalformedHeaderDefect` -- A header was found that was missing a " "colon, or was otherwise malformed." msgstr "" #: ../Doc/library/email.errors.rst:96 msgid "This defect has not been used for several Python versions." msgstr "" #: ../Doc/library/email.errors.rst:99 msgid "" ":class:`MultipartInvariantViolationDefect` -- A message claimed to be a :" "mimetype:`multipart`, but no subparts were found. Note that when a message " "has this defect, its :meth:`~email.message.Message.is_multipart` method may " "return false even though its content type claims to be :mimetype:`multipart`." msgstr "" #: ../Doc/library/email.errors.rst:104 msgid "" ":class:`InvalidBase64PaddingDefect` -- When decoding a block of base64 " "enocded bytes, the padding was not correct. Enough padding is added to " "perform the decode, but the resulting decoded bytes may be invalid." msgstr "" #: ../Doc/library/email.errors.rst:108 msgid "" ":class:`InvalidBase64CharactersDefect` -- When decoding a block of base64 " "enocded bytes, characters outside the base64 alphebet were encountered. The " "characters are ignored, but the resulting decoded bytes may be invalid." msgstr ""