espoir/python-docs-fr
Fork 0
forked from AFPy/python-docs-fr
Code Pull requests Activity

3.8: New files.

Browse source
This commit is contained in:
Julien Palard 2019-09-04 11:39:22 +02:00
commit 1dabb7ef74
6 changed files with 4089 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

40
library/audit_events.po Normal file
View file

@ -0,0 +1,40 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2019, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.8\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-09-04 11:33+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../Doc/library/audit_events.rst:6
msgid "Audit events table"
msgstr ""
#: ../Doc/library/audit_events.rst:8
msgid ""
"This table contains all events raised by :func:`sys.audit` or :c:func:"
"`PySys_Audit` calls throughout the CPython runtime and the standard library."
msgstr ""
#: ../Doc/library/audit_events.rst:12
msgid ""
"See :func:`sys.addaudithook` and :c:func:`PySys_AddAuditHook` for "
"information on handling these events."
msgstr ""
#: ../Doc/library/audit_events.rst:17
msgid ""
"This table is generated from the CPython documentation, and may not "
"represent events raised by other implementations. See your runtime specific "
"documentation for actual events raised."
msgstr ""

257
library/importlib.metadata.po Normal file
View file

@ -0,0 +1,257 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2019, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.8\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-09-04 11:33+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../Doc/library/importlib.metadata.rst:5
msgid "Using importlib.metadata"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:8
msgid ""
"This functionality is provisional and may deviate from the usual version "
"semantics of the standard library."
msgstr ""
#: ../Doc/library/importlib.metadata.rst:11
msgid ""
"``importlib.metadata`` is a library that provides for access to installed "
"package metadata. Built in part on Python's import system, this library "
"intends to replace similar functionality in the `entry point API`_ and "
"`metadata API`_ of ``pkg_resources``. Along with ``importlib.resources`` in "
"`Python 3.7 and newer`_ (backported as `importlib_resources`_ for older "
"versions of Python), this can eliminate the need to use the older and less "
"efficient ``pkg_resources`` package."
msgstr ""
#: ../Doc/library/importlib.metadata.rst:20
msgid ""
"By \"installed package\" we generally mean a third-party package installed "
"into Python's ``site-packages`` directory via tools such as `pip <https://"
"pypi.org/project/pip/>`_. Specifically, it means a package with either a "
"discoverable ``dist-info`` or ``egg-info`` directory, and metadata defined "
"by `PEP 566`_ or its older specifications. By default, package metadata can "
"live on the file system or in zip archives on ``sys.path``. Through an "
"extension mechanism, the metadata can live almost anywhere."
msgstr ""
#: ../Doc/library/importlib.metadata.rst:31
msgid "Overview"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:33
msgid ""
"Let's say you wanted to get the version string for a package you've "
"installed using ``pip``. We start by creating a virtual environment and "
"installing something into it:"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:43
msgid "You can get the version string for ``wheel`` by running the following:"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:52
msgid ""
"You can also get the set of entry points keyed by group, such as "
"``console_scripts``, ``distutils.commands`` and others. Each group contains "
"a sequence of :ref:`EntryPoint <entry-points>` objects."
msgstr ""
#: ../Doc/library/importlib.metadata.rst:56
msgid "You can get the :ref:`metadata for a distribution <metadata>`::"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:61
msgid ""
"You can also get a :ref:`distribution's version number <version>`, list its :"
"ref:`constituent files <files>`, and get a list of the distribution's :ref:"
"`requirements`."
msgstr ""
#: ../Doc/library/importlib.metadata.rst:67
msgid "Functional API"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:69
msgid "This package provides the following functionality via its public API."
msgstr ""
#: ../Doc/library/importlib.metadata.rst:75
msgid "Entry points"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:77
msgid ""
"The ``entry_points()`` function returns a dictionary of all entry points, "
"keyed by group. Entry points are represented by ``EntryPoint`` instances; "
"each ``EntryPoint`` has a ``.name``, ``.group``, and ``.value`` attributes "
"and a ``.load()`` method to resolve the value."
msgstr ""
#: ../Doc/library/importlib.metadata.rst:93
msgid ""
"The ``group`` and ``name`` are arbitrary values defined by the package "
"author and usually a client will wish to resolve all entry points for a "
"particular group. Read `the setuptools docs <https://setuptools.readthedocs."
"io/en/latest/setuptools.html#dynamic-discovery-of-services-and-plugins>`_ "
"for more information on entrypoints, their definition, and usage."
msgstr ""
#: ../Doc/library/importlib.metadata.rst:103
msgid "Distribution metadata"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:105
msgid ""
"Every distribution includes some metadata, which you can extract using the "
"``metadata()`` function::"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:110
msgid ""
"The keys of the returned data structure [#f1]_ name the metadata keywords, "
"and their values are returned unparsed from the distribution metadata::"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:120
msgid "Distribution versions"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:122
msgid ""
"The ``version()`` function is the quickest way to get a distribution's "
"version number, as a string::"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:132
msgid "Distribution files"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:134
msgid ""
"You can also get the full set of files contained within a distribution. The "
"``files()`` function takes a distribution package name and returns all of "
"the files installed by this distribution. Each file object returned is a "
"``PackagePath``, a `pathlib.Path`_ derived object with additional ``dist``, "
"``size``, and ``hash`` properties as indicated by the metadata. For "
"example::"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:150
msgid "Once you have the file, you can also read its contents::"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:161
msgid ""
"In the case where the metadata file listing files (RECORD or SOURCES.txt) is "
"missing, ``files()`` will return ``None``. The caller may wish to wrap calls "
"to ``files()`` in `always_iterable <https://more-itertools.readthedocs.io/en/"
"stable/api.html#more_itertools.always_iterable>`_ or otherwise guard against "
"this condition if the target distribution is not known to have the metadata "
"present."
msgstr ""
#: ../Doc/library/importlib.metadata.rst:172
msgid "Distribution requirements"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:174
msgid ""
"To get the full set of requirements for a distribution, use the "
"``requires()`` function. Note that this returns an iterator::"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:182
msgid "Distributions"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:184
msgid ""
"While the above API is the most common and convenient usage, you can get all "
"of that information from the ``Distribution`` class. A ``Distribution`` is "
"an abstract object that represents the metadata for a Python package. You "
"can get the ``Distribution`` instance::"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:192
msgid ""
"Thus, an alternative way to get the version number is through the "
"``Distribution`` instance::"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:198
msgid ""
"There are all kinds of additional metadata available on the ``Distribution`` "
"instance::"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:206
msgid ""
"The full set of available metadata is not described here. See `PEP 566 "
"<https://www.python.org/dev/peps/pep-0566/>`_ for additional details."
msgstr ""
#: ../Doc/library/importlib.metadata.rst:211
msgid "Extending the search algorithm"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:213
msgid ""
"Because package metadata is not available through ``sys.path`` searches, or "
"package loaders directly, the metadata for a package is found through import "
"system `finders`_. To find a distribution package's metadata, ``importlib."
"metadata`` queries the list of `meta path finders`_ on `sys.meta_path`_."
msgstr ""
#: ../Doc/library/importlib.metadata.rst:219
msgid ""
"By default ``importlib.metadata`` installs a finder for distribution "
"packages found on the file system. This finder doesn't actually find any "
"*packages*, but it can find the packages' metadata."
msgstr ""
#: ../Doc/library/importlib.metadata.rst:223
msgid ""
"The abstract class :py:class:`importlib.abc.MetaPathFinder` defines the "
"interface expected of finders by Python's import system. ``importlib."
"metadata`` extends this protocol by looking for an optional "
"``find_distributions`` callable on the finders from ``sys.meta_path``. If "
"the finder has this method, it must return an iterator over instances of the "
"``Distribution`` abstract class. This method must have the signature::"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:238
msgid ""
"What this means in practice is that to support finding distribution package "
"metadata in locations other than the file system, you should derive from "
"``Distribution`` and implement the ``load_metadata()`` method. This takes a "
"single argument which is the name of the package whose metadata is being "
"found. This instance of the ``Distribution`` base abstract class is what "
"your finder's ``find_distributions()`` method should return."
msgstr ""
#: ../Doc/library/importlib.metadata.rst:258
msgid "Footnotes"
msgstr ""
#: ../Doc/library/importlib.metadata.rst:259
msgid ""
"Technically, the returned distribution metadata object is an `email.message."
"Message <https://docs.python.org/3/library/email.message.html#email.message."
"EmailMessage>`_ instance, but this is an implementation detail, and not part "
"of the stable API. You should only use dictionary-like methods and syntax "
"to access the metadata contents."
msgstr ""