forked from AFPy/python-docs-fr
340 lines
12 KiB
Plaintext
340 lines
12 KiB
Plaintext
# Copyright (C) 2001-2018, Python Software Foundation
|
|
# For licence information, see README file.
|
|
#
|
|
msgid ""
|
|
msgstr ""
|
|
"Project-Id-Version: Python 3\n"
|
|
"Report-Msgid-Bugs-To: \n"
|
|
"POT-Creation-Date: 2020-02-04 10:00+0100\n"
|
|
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
|
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
|
"Language-Team: FRENCH <traductions@lists.afpy.org>\n"
|
|
"Language: fr\n"
|
|
"MIME-Version: 1.0\n"
|
|
"Content-Type: text/plain; charset=UTF-8\n"
|
|
"Content-Transfer-Encoding: 8bit\n"
|
|
|
|
#: ../Doc/distutils/introduction.rst:5
|
|
msgid "An Introduction to Distutils"
|
|
msgstr ""
|
|
|
|
#: Doc/distutils/_setuptools_disclaimer.rst:3
|
|
msgid ""
|
|
"This document is being retained solely until the ``setuptools`` "
|
|
"documentation at https://setuptools.readthedocs.io/en/latest/setuptools.html "
|
|
"independently covers all of the relevant information currently included here."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:9
|
|
msgid ""
|
|
"This document covers using the Distutils to distribute your Python modules, "
|
|
"concentrating on the role of developer/distributor: if you're looking for "
|
|
"information on installing Python modules, you should refer to the :ref:"
|
|
"`install-index` chapter."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:18
|
|
msgid "Concepts & Terminology"
|
|
msgstr "Concepts et Terminologie"
|
|
|
|
#: ../Doc/distutils/introduction.rst:20
|
|
msgid ""
|
|
"Using the Distutils is quite simple, both for module developers and for "
|
|
"users/administrators installing third-party modules. As a developer, your "
|
|
"responsibilities (apart from writing solid, well-documented and well-tested "
|
|
"code, of course!) are:"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:25
|
|
msgid "write a setup script (:file:`setup.py` by convention)"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:27
|
|
msgid "(optional) write a setup configuration file"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:29
|
|
msgid "create a source distribution"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:31
|
|
msgid "(optional) create one or more built (binary) distributions"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:33
|
|
msgid "Each of these tasks is covered in this document."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:35
|
|
msgid ""
|
|
"Not all module developers have access to a multitude of platforms, so it's "
|
|
"not always feasible to expect them to create a multitude of built "
|
|
"distributions. It is hoped that a class of intermediaries, called "
|
|
"*packagers*, will arise to address this need. Packagers will take source "
|
|
"distributions released by module developers, build them on one or more "
|
|
"platforms, and release the resulting built distributions. Thus, users on "
|
|
"the most popular platforms will be able to install most popular Python "
|
|
"module distributions in the most natural way for their platform, without "
|
|
"having to run a single setup script or compile a line of code."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:49
|
|
msgid "A Simple Example"
|
|
msgstr "Un exemple simple"
|
|
|
|
#: ../Doc/distutils/introduction.rst:51
|
|
msgid ""
|
|
"The setup script is usually quite simple, although since it's written in "
|
|
"Python, there are no arbitrary limits to what you can do with it, though you "
|
|
"should be careful about putting arbitrarily expensive operations in your "
|
|
"setup script. Unlike, say, Autoconf-style configure scripts, the setup "
|
|
"script may be run multiple times in the course of building and installing "
|
|
"your module distribution."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:58
|
|
msgid ""
|
|
"If all you want to do is distribute a module called :mod:`foo`, contained in "
|
|
"a file :file:`foo.py`, then your setup script can be as simple as this::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:67
|
|
msgid "Some observations:"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:69
|
|
msgid ""
|
|
"most information that you supply to the Distutils is supplied as keyword "
|
|
"arguments to the :func:`setup` function"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:72
|
|
msgid ""
|
|
"those keyword arguments fall into two categories: package metadata (name, "
|
|
"version number) and information about what's in the package (a list of pure "
|
|
"Python modules, in this case)"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:76
|
|
msgid ""
|
|
"modules are specified by module name, not filename (the same will hold true "
|
|
"for packages and extensions)"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:79
|
|
msgid ""
|
|
"it's recommended that you supply a little more metadata, in particular your "
|
|
"name, email address and a URL for the project (see section :ref:`setup-"
|
|
"script` for an example)"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:83
|
|
msgid ""
|
|
"To create a source distribution for this module, you would create a setup "
|
|
"script, :file:`setup.py`, containing the above code, and run this command "
|
|
"from a terminal::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:89
|
|
msgid ""
|
|
"For Windows, open a command prompt window (:menuselection:`Start --> "
|
|
"Accessories`) and change the command to::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:94
|
|
msgid ""
|
|
":command:`sdist` will create an archive file (e.g., tarball on Unix, ZIP "
|
|
"file on Windows) containing your setup script :file:`setup.py`, and your "
|
|
"module :file:`foo.py`. The archive file will be named :file:`foo-1.0.tar.gz` "
|
|
"(or :file:`.zip`), and will unpack into a directory :file:`foo-1.0`."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:99
|
|
msgid ""
|
|
"If an end-user wishes to install your :mod:`foo` module, all they have to do "
|
|
"is download :file:`foo-1.0.tar.gz` (or :file:`.zip`), unpack it, and---from "
|
|
"the :file:`foo-1.0` directory---run ::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:105
|
|
msgid ""
|
|
"which will ultimately copy :file:`foo.py` to the appropriate directory for "
|
|
"third-party modules in their Python installation."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:108
|
|
msgid ""
|
|
"This simple example demonstrates some fundamental concepts of the Distutils. "
|
|
"First, both developers and installers have the same basic user interface, i."
|
|
"e. the setup script. The difference is which Distutils *commands* they use: "
|
|
"the :command:`sdist` command is almost exclusively for module developers, "
|
|
"while :command:`install` is more often for installers (although most "
|
|
"developers will want to install their own code occasionally)."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:115
|
|
msgid ""
|
|
"If you want to make things really easy for your users, you can create one or "
|
|
"more built distributions for them. For instance, if you are running on a "
|
|
"Windows machine, and want to make things easy for other Windows users, you "
|
|
"can create an executable installer (the most appropriate type of built "
|
|
"distribution for this platform) with the :command:`bdist_wininst` command. "
|
|
"For example::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:123
|
|
msgid ""
|
|
"will create an executable installer, :file:`foo-1.0.win32.exe`, in the "
|
|
"current directory."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:126
|
|
msgid ""
|
|
"Other useful built distribution formats are RPM, implemented by the :command:"
|
|
"`bdist_rpm` command, Solaris :program:`pkgtool` (:command:`bdist_pkgtool`), "
|
|
"and HP-UX :program:`swinstall` (:command:`bdist_sdux`). For example, the "
|
|
"following command will create an RPM file called :file:`foo-1.0.noarch.rpm`::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:134
|
|
msgid ""
|
|
"(The :command:`bdist_rpm` command uses the :command:`rpm` executable, "
|
|
"therefore this has to be run on an RPM-based system such as Red Hat Linux, "
|
|
"SuSE Linux, or Mandrake Linux.)"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:138
|
|
msgid ""
|
|
"You can find out what distribution formats are available at any time by "
|
|
"running ::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:147
|
|
msgid "General Python terminology"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:149
|
|
msgid ""
|
|
"If you're reading this document, you probably have a good idea of what "
|
|
"modules, extensions, and so forth are. Nevertheless, just to be sure that "
|
|
"everyone is operating from a common starting point, we offer the following "
|
|
"glossary of common Python terms:"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:157
|
|
msgid "module"
|
|
msgstr "module"
|
|
|
|
#: ../Doc/distutils/introduction.rst:155
|
|
msgid ""
|
|
"the basic unit of code reusability in Python: a block of code imported by "
|
|
"some other code. Three types of modules concern us here: pure Python "
|
|
"modules, extension modules, and packages."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:162
|
|
msgid "pure Python module"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:160
|
|
msgid ""
|
|
"a module written in Python and contained in a single :file:`.py` file (and "
|
|
"possibly associated :file:`.pyc` files). Sometimes referred to as a \"pure "
|
|
"module.\""
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:170
|
|
msgid "extension module"
|
|
msgstr "module d'extension"
|
|
|
|
#: ../Doc/distutils/introduction.rst:165
|
|
msgid ""
|
|
"a module written in the low-level language of the Python implementation: C/C+"
|
|
"+ for Python, Java for Jython. Typically contained in a single dynamically "
|
|
"loadable pre-compiled file, e.g. a shared object (:file:`.so`) file for "
|
|
"Python extensions on Unix, a DLL (given the :file:`.pyd` extension) for "
|
|
"Python extensions on Windows, or a Java class file for Jython extensions. "
|
|
"(Note that currently, the Distutils only handles C/C++ extensions for "
|
|
"Python.)"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:175
|
|
msgid "package"
|
|
msgstr "paquet"
|
|
|
|
#: ../Doc/distutils/introduction.rst:173
|
|
msgid ""
|
|
"a module that contains other modules; typically contained in a directory in "
|
|
"the filesystem and distinguished from other directories by the presence of a "
|
|
"file :file:`__init__.py`."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:185
|
|
msgid "root package"
|
|
msgstr "paquet racine"
|
|
|
|
#: ../Doc/distutils/introduction.rst:178
|
|
msgid ""
|
|
"the root of the hierarchy of packages. (This isn't really a package, since "
|
|
"it doesn't have an :file:`__init__.py` file. But we have to call it "
|
|
"something.) The vast majority of the standard library is in the root "
|
|
"package, as are many small, standalone third-party modules that don't belong "
|
|
"to a larger module collection. Unlike regular packages, modules in the root "
|
|
"package can be found in many directories: in fact, every directory listed in "
|
|
"``sys.path`` contributes modules to the root package."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:190
|
|
msgid "Distutils-specific terminology"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:192
|
|
msgid ""
|
|
"The following terms apply more specifically to the domain of distributing "
|
|
"Python modules using the Distutils:"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:201
|
|
msgid "module distribution"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:196
|
|
msgid ""
|
|
"a collection of Python modules distributed together as a single downloadable "
|
|
"resource and meant to be installed *en masse*. Examples of some well-known "
|
|
"module distributions are NumPy, SciPy, Pillow, or mxBase. (This would be "
|
|
"called a *package*, except that term is already taken in the Python context: "
|
|
"a single module distribution may contain zero, one, or many Python packages.)"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:205
|
|
msgid "pure module distribution"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:204
|
|
msgid ""
|
|
"a module distribution that contains only pure Python modules and packages. "
|
|
"Sometimes referred to as a \"pure distribution.\""
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:209
|
|
msgid "non-pure module distribution"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:208
|
|
msgid ""
|
|
"a module distribution that contains at least one extension module. "
|
|
"Sometimes referred to as a \"non-pure distribution.\""
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:213
|
|
msgid "distribution root"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/introduction.rst:212
|
|
msgid ""
|
|
"the top-level directory of your source tree (or source distribution); the "
|
|
"directory where :file:`setup.py` exists. Generally :file:`setup.py` will "
|
|
"be run from this directory."
|
|
msgstr ""
|