forked from AFPy/python-docs-fr
1736 lines
70 KiB
Plaintext
1736 lines
70 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-10-01 16:00+0200\n"
|
||
"PO-Revision-Date: 2020-04-27 22:25+0200\n"
|
||
"Last-Translator: Julien Palard <julien@palard.fr>\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"
|
||
"X-Generator: Poedit 2.2.3\n"
|
||
|
||
#: install/index.rst:7
|
||
msgid "Installing Python Modules (Legacy version)"
|
||
msgstr "Installation des modules python (Version historique)"
|
||
|
||
#: install/index.rst:0
|
||
msgid "Author"
|
||
msgstr "Auteur"
|
||
|
||
#: install/index.rst:9
|
||
msgid "Greg Ward"
|
||
msgstr "Greg Ward"
|
||
|
||
#: install/index.rst:16
|
||
msgid ":ref:`installing-index`"
|
||
msgstr ":ref:`installing-index`"
|
||
|
||
#: install/index.rst:16
|
||
msgid ""
|
||
"The up to date module installation documentation. For regular Python usage, "
|
||
"you almost certainly want that document rather than this one."
|
||
msgstr ""
|
||
"le document à jour pour l'installation des modules. Pour une utilisation "
|
||
"normale de Python, c'est ce document que vous cherchez plutôt que celui-ci."
|
||
|
||
#: 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 ""
|
||
"Cette page est conservée uniquement jusqu'à ce que la documentation "
|
||
"``setuptool`` sur https://setuptools.readthedocs.io/en/latest/setuptools."
|
||
"html couvre de manière indépendante toutes les informations pertinentes "
|
||
"actuellement incluses ici."
|
||
|
||
#: install/index.rst:23
|
||
msgid ""
|
||
"This guide only covers the basic tools for building and distributing "
|
||
"extensions that are provided as part of this version of Python. Third party "
|
||
"tools offer easier to use and more secure alternatives. Refer to the `quick "
|
||
"recommendations section <https://packaging.python.org/guides/tool-"
|
||
"recommendations/>`__ in the Python Packaging User Guide for more information."
|
||
msgstr ""
|
||
"Ce guide ne couvre que les outils de base, fournis avec cette version de "
|
||
"Python, pour construire et distribuer des extensions. D'autres outils "
|
||
"peuvent être plus sécurisés et plus simple à utiliser. Consultez `quick "
|
||
"recommendations section <https://packaging.python.org/guides/tool-"
|
||
"recommendations/>`__ dans le *Python Packaging User Guide* pour plus "
|
||
"d'informations."
|
||
|
||
#: install/index.rst:34
|
||
msgid "Introduction"
|
||
msgstr "Introduction"
|
||
|
||
#: install/index.rst:36
|
||
msgid ""
|
||
"In Python 2.0, the ``distutils`` API was first added to the standard "
|
||
"library. This provided Linux distro maintainers with a standard way of "
|
||
"converting Python projects into Linux distro packages, and system "
|
||
"administrators with a standard way of installing them directly onto target "
|
||
"systems."
|
||
msgstr ""
|
||
"Dans Python 2.0, l'API ``distutils`` a d'abord été ajoutée à la bibliothèque "
|
||
"standard. Elle a donné aux mainteneurs de distributions Linux une façon "
|
||
"standard d'intégrer des projets Python dans les paquets Linux, et aux "
|
||
"administrateurs système une façon standard de les installer directement sur "
|
||
"les systèmes cibles."
|
||
|
||
#: install/index.rst:41
|
||
msgid ""
|
||
"In the many years since Python 2.0 was released, tightly coupling the build "
|
||
"system and package installer to the language runtime release cycle has "
|
||
"turned out to be problematic, and it is now recommended that projects use "
|
||
"the ``pip`` package installer and the ``setuptools`` build system, rather "
|
||
"than using ``distutils`` directly."
|
||
msgstr ""
|
||
"À l'époque où Python 2.0 a été publié, le fort couplage entre le système "
|
||
"d'intégration et le gestionnaire de paquets avec le cycle de publication du "
|
||
"langage était problématique, et il est désormais recommandé d'utiliser le "
|
||
"gestionnaire de paquets ``pip`` ainsi que le système d'intégration "
|
||
"``setuptools`` plutôt que d'utiliser ``distutils`` directement."
|
||
|
||
#: install/index.rst:47
|
||
msgid ""
|
||
"See :ref:`installing-index` and :ref:`distributing-index` for more details."
|
||
msgstr ""
|
||
"Voir :ref:`installing-index` et :ref:`distributing-index` pour plus de "
|
||
"détails."
|
||
|
||
#: install/index.rst:49
|
||
msgid ""
|
||
"This legacy documentation is being retained only until we're confident that "
|
||
"the ``setuptools`` documentation covers everything needed."
|
||
msgstr ""
|
||
"Cette ancienne documentation sera conservée jusqu'à ce que nous soyons "
|
||
"certains que la documentation sur ``setuptools`` couvre tout ce qui est "
|
||
"nécessaire."
|
||
|
||
#: install/index.rst:55
|
||
msgid "Distutils based source distributions"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:57
|
||
msgid ""
|
||
"If you download a module source distribution, you can tell pretty quickly if "
|
||
"it was packaged and distributed in the standard way, i.e. using the "
|
||
"Distutils. First, the distribution's name and version number will be "
|
||
"featured prominently in the name of the downloaded archive, e.g. :file:"
|
||
"`foo-1.0.tar.gz` or :file:`widget-0.9.7.zip`. Next, the archive will unpack "
|
||
"into a similarly-named directory: :file:`foo-1.0` or :file:`widget-0.9.7`. "
|
||
"Additionally, the distribution will contain a setup script :file:`setup.py`, "
|
||
"and a file named :file:`README.txt` or possibly just :file:`README`, which "
|
||
"should explain that building and installing the module distribution is a "
|
||
"simple matter of running one command from a terminal::"
|
||
msgstr ""
|
||
"Si vous téléchargez une distribution source du module, vous pouvez dire "
|
||
"assez rapidement s'il a été empaqueté et distribué de la façon standard, "
|
||
"c'est-à-dire en utilisant Distutils. Premièrement, le nom et le numéro de "
|
||
"version de la distribution sont affichés en bonne place dans le nom de "
|
||
"l'archive téléchargée, par exemple :file:`foo-1.0.tar.gz` ou :file:"
|
||
"`widget-0.9.7.zip`. Ensuite, l'archive se décompresse dans un répertoire du "
|
||
"même nom : :file:`foo-1.0` ou :file:`widget-0.9.7`. En outre, la "
|
||
"distribution contient un script d'installation :file:`setup.py` et un "
|
||
"fichier nommé :file:`README.txt` ou éventuellement juste :file:`README`, qui "
|
||
"doit expliquer que la construction et l'installation de la distribution du "
|
||
"module se fait simplement en exécutant ceci ::"
|
||
|
||
#: install/index.rst:70
|
||
msgid ""
|
||
"For Windows, this command should be run from a command prompt window (:"
|
||
"menuselection:`Start --> Accessories`)::"
|
||
msgstr ""
|
||
"Sous Windows, cette commande doit être lancée depuis une invite de commande "
|
||
"(:menuselection:`Démarrer --> Accessoires`) ::"
|
||
|
||
#: install/index.rst:75
|
||
msgid ""
|
||
"If all these things are true, then you already know how to build and install "
|
||
"the modules you've just downloaded: Run the command above. Unless you need "
|
||
"to install things in a non-standard way or customize the build process, you "
|
||
"don't really need this manual. Or rather, the above command is everything "
|
||
"you need to get out of this manual."
|
||
msgstr ""
|
||
"Si toutes ces choses sont vérifiées, alors vous savez déjà comment "
|
||
"construire et installer le module que vous venez de télécharger : en "
|
||
"exécutant la commande ci-dessus. Sauf si vous avez besoin d'installer les "
|
||
"choses d'une manière non standard ou de personnaliser le processus de "
|
||
"construction, vous n'avez pas vraiment besoin de ce manuel. Ou plutôt, la "
|
||
"commande ci-dessus est tout ce dont vous avez besoin de retenir de ce manuel."
|
||
|
||
#: install/index.rst:85
|
||
msgid "Standard Build and Install"
|
||
msgstr "Construction standard et installation"
|
||
|
||
#: install/index.rst:87
|
||
msgid ""
|
||
"As described in section :ref:`inst-new-standard`, building and installing a "
|
||
"module distribution using the Distutils is usually one simple command to run "
|
||
"from a terminal::"
|
||
msgstr ""
|
||
"Comme décrit dans la section :ref:`inst-new-standard`, construire et "
|
||
"installer une distribution de modules en utilisant les Distutils consiste "
|
||
"généralement à exécuter une simple commande dans un terminal ::"
|
||
|
||
#: install/index.rst:97
|
||
msgid "Platform variations"
|
||
msgstr "Différences selon les plateformes"
|
||
|
||
#: install/index.rst:99
|
||
msgid ""
|
||
"You should always run the setup command from the distribution root "
|
||
"directory, i.e. the top-level subdirectory that the module source "
|
||
"distribution unpacks into. For example, if you've just downloaded a module "
|
||
"source distribution :file:`foo-1.0.tar.gz` onto a Unix system, the normal "
|
||
"thing to do is::"
|
||
msgstr ""
|
||
"Vous devez toujours exécuter la commande *setup* à partir du répertoire "
|
||
"racine de la distribution, à savoir le sous-répertoire de plus haut niveau "
|
||
"dans l'arborescence où se sont décompressées les sources de la distribution "
|
||
"du module. Par exemple, si vous venez de télécharger les sources d'une "
|
||
"distribution du module :file:`foo-1.0.tar.gz` sous un système UNIX, la "
|
||
"méthode normale consiste à faire ::"
|
||
|
||
#: install/index.rst:108
|
||
msgid ""
|
||
"On Windows, you'd probably download :file:`foo-1.0.zip`. If you downloaded "
|
||
"the archive file to :file:`C:\\\\Temp`, then it would unpack into :file:`C:\\"
|
||
"\\Temp\\\\foo-1.0`; you can use either an archive manipulator with a "
|
||
"graphical user interface (such as WinZip) or a command-line tool (such as :"
|
||
"program:`unzip` or :program:`pkunzip`) to unpack the archive. Then, open a "
|
||
"command prompt window and run::"
|
||
msgstr ""
|
||
"Sous Windows, vous avez probablement téléchargé :file:`foo-1.0.zip`. Si vous "
|
||
"avez téléchargé le fichier d'archive dans :file:`C:\\\\Temp`, il se "
|
||
"décompressera alors dans :file:`C:\\\\Temp\\\\foo-1.0` ; vous pouvez "
|
||
"utiliser soit un gestionnaire d'archives graphique (comme WinZip), soit un "
|
||
"outil de ligne de commande (tels que :program:`unzip` ou :program:`pkunzip`) "
|
||
"pour décompresser l'archive. Ensuite, ouvrez une fenêtre d'invite de "
|
||
"commandes et exécutez ::"
|
||
|
||
#: install/index.rst:122
|
||
msgid "Splitting the job up"
|
||
msgstr "Fractionnement du travail"
|
||
|
||
#: install/index.rst:124
|
||
msgid ""
|
||
"Running ``setup.py install`` builds and installs all modules in one run. If "
|
||
"you prefer to work incrementally---especially useful if you want to "
|
||
"customize the build process, or if things are going wrong---you can use the "
|
||
"setup script to do one thing at a time. This is particularly helpful when "
|
||
"the build and install will be done by different users---for example, you "
|
||
"might want to build a module distribution and hand it off to a system "
|
||
"administrator for installation (or do it yourself, with super-user "
|
||
"privileges)."
|
||
msgstr ""
|
||
"Exécuter ``setup.py install`` construit et installe tous les modules en un "
|
||
"seul coup. Si vous préférez travailler progressivement — ce qui est "
|
||
"particulièrement utile si vous souhaitez personnaliser le processus de "
|
||
"construction ou si les choses vont mal — vous pouvez utiliser le script de "
|
||
"configuration pour faire une chose à la fois. Cela est particulièrement "
|
||
"utile lorsque la construction et l'installation doit être faite par "
|
||
"différents utilisateurs — par exemple, vous pouvez vouloir construire une "
|
||
"distribution d'un module et la transférer à un administrateur système pour "
|
||
"l'installation (ou le faire vous-même, avec les privilèges de super-"
|
||
"utilisateur)."
|
||
|
||
#: install/index.rst:132
|
||
msgid ""
|
||
"For example, you can build everything in one step, and then install "
|
||
"everything in a second step, by invoking the setup script twice::"
|
||
msgstr ""
|
||
"Par exemple, vous pouvez construire tout en une seule étape et ensuite "
|
||
"installer le tout dans une deuxième étape, en invoquant le script "
|
||
"d'installation deux fois ::"
|
||
|
||
#: install/index.rst:138
|
||
msgid ""
|
||
"If you do this, you will notice that running the :command:`install` command "
|
||
"first runs the :command:`build` command, which---in this case---quickly "
|
||
"notices that it has nothing to do, since everything in the :file:`build` "
|
||
"directory is up-to-date."
|
||
msgstr ""
|
||
"Si vous faites cela, vous remarquerez que l'exécution de la commande :"
|
||
"command:`install` lance d'abord la commande :command:`build`, qui, dans ce "
|
||
"cas, s'aperçoit vite qu'il n'a rien à faire, puisque tout dans le dossier :"
|
||
"file:`build` est à jour."
|
||
|
||
#: install/index.rst:143
|
||
msgid ""
|
||
"You may not need this ability to break things down often if all you do is "
|
||
"install modules downloaded off the 'net, but it's very handy for more "
|
||
"advanced tasks. If you get into distributing your own Python modules and "
|
||
"extensions, you'll run lots of individual Distutils commands on their own."
|
||
msgstr ""
|
||
"Il se peut que vous n'ayez pas souvent besoin de cette capacité à séparer "
|
||
"les étapes si tout ce que vous faites est d'installer les modules "
|
||
"téléchargés sur le Net, mais c'est très pratique pour des tâches plus "
|
||
"avancées. Si vous en venez à distribuer vos propres modules et extensions "
|
||
"Python, vous allez exécuter beaucoup de commandes individuelles de "
|
||
"Distutils, indépendamment les unes des autres."
|
||
|
||
#: install/index.rst:152
|
||
msgid "How building works"
|
||
msgstr "Comment fonctionne une construction"
|
||
|
||
#: install/index.rst:154
|
||
msgid ""
|
||
"As implied above, the :command:`build` command is responsible for putting "
|
||
"the files to install into a *build directory*. By default, this is :file:"
|
||
"`build` under the distribution root; if you're excessively concerned with "
|
||
"speed, or want to keep the source tree pristine, you can change the build "
|
||
"directory with the :option:`!--build-base` option. For example::"
|
||
msgstr ""
|
||
"Comme sous-entendu ci-dessus, la commande :command:`build` est chargée de "
|
||
"mettre les fichiers à installer dans un *répertoire de travail*. Par défaut, "
|
||
"c'est :file:`build` à la racine de la distribution ; si vous êtes très "
|
||
"préoccupés par la vitesse, ou si vous voulez conserver l'arborescence des "
|
||
"sources d'origine, vous pouvez changer le répertoire de construction avec "
|
||
"l'option :option:`!--build-base`. Par exemple ::"
|
||
|
||
#: install/index.rst:162
|
||
msgid ""
|
||
"(Or you could do this permanently with a directive in your system or "
|
||
"personal Distutils configuration file; see section :ref:`inst-config-"
|
||
"files`.) Normally, this isn't necessary."
|
||
msgstr ""
|
||
"(Ou vous pourriez le faire de façon permanente avec une directive dans votre "
|
||
"système ou dans le fichier de configuration personnelle de Distutils ; voir "
|
||
"la section :ref:`inst-config-files`.) Normalement, ce n'est pas nécessaire."
|
||
|
||
#: install/index.rst:166
|
||
msgid "The default layout for the build tree is as follows::"
|
||
msgstr ""
|
||
"L'arborescence par défaut produite par la compilation se présente comme "
|
||
"suit ::"
|
||
|
||
#: install/index.rst:173
|
||
msgid ""
|
||
"where ``<plat>`` expands to a brief description of the current OS/hardware "
|
||
"platform and Python version. The first form, with just a :file:`lib` "
|
||
"directory, is used for \"pure module distributions\"---that is, module "
|
||
"distributions that include only pure Python modules. If a module "
|
||
"distribution contains any extensions (modules written in C/C++), then the "
|
||
"second form, with two ``<plat>`` directories, is used. In that case, the :"
|
||
"file:`temp.{plat}` directory holds temporary files generated by the compile/"
|
||
"link process that don't actually get installed. In either case, the :file:"
|
||
"`lib` (or :file:`lib.{plat}`) directory contains all Python modules (pure "
|
||
"Python and extensions) that will be installed."
|
||
msgstr ""
|
||
"où ``<plat>`` représente une brève description de l'actuel système "
|
||
"d'exploitation / plateforme matérielle et la version Python. La première "
|
||
"forme, avec juste un dossier :file:`lib` est utilisée pour les "
|
||
"« distributions de modules purs » — c'est-à-dire des distributions de module "
|
||
"qui n'incorporent que des modules en Python. Si un module de la distribution "
|
||
"contient au moins une extension (modules écrits en C/C++), alors il faut "
|
||
"utiliser la deuxième forme, avec deux dossiers ``<plat>``. Dans ce cas, le "
|
||
"répertoire :file:`temp.{plat}` contient les fichiers temporaires générés par "
|
||
"le processus de compilation et de génération de liens (ils ne seront pas "
|
||
"installés). Dans les deux cas, le dossier :file:`lib` (ou :file:`lib.{plat}"
|
||
"`) contient tous les modules Python (Python pur et extensions) qui seront "
|
||
"installés."
|
||
|
||
#: install/index.rst:183
|
||
msgid ""
|
||
"In the future, more directories will be added to handle Python scripts, "
|
||
"documentation, binary executables, and whatever else is needed to handle the "
|
||
"job of installing Python modules and applications."
|
||
msgstr ""
|
||
"Dans l'avenir, d'autres répertoires seront ajoutés pour gérer les scripts "
|
||
"Python, de la documentation, des exécutables binaires et tout ce qui est "
|
||
"nécessaire pour gérer le travail de l'installation de modules et "
|
||
"d'applications Python."
|
||
|
||
#: install/index.rst:191
|
||
msgid "How installation works"
|
||
msgstr "Comment fonctionne l'installation"
|
||
|
||
#: install/index.rst:193
|
||
msgid ""
|
||
"After the :command:`build` command runs (whether you run it explicitly, or "
|
||
"the :command:`install` command does it for you), the work of the :command:"
|
||
"`install` command is relatively simple: all it has to do is copy everything "
|
||
"under :file:`build/lib` (or :file:`build/lib.{plat}`) to your chosen "
|
||
"installation directory."
|
||
msgstr ""
|
||
"Après l'exécution de la commande :command:`build` (que vous l'ayez exécutée "
|
||
"explicitement ou que la commande :command:`install` l'ait fait pour vous), "
|
||
"le travail de la commande :command:`install` est relativement simple : tout "
|
||
"ce qu'il a à faire est de copier tout ce qui est sous :file:`build/lib` (ou :"
|
||
"file:`build/lib.{plat}`) dans le répertoire que vous avez choisi pour "
|
||
"l'installation."
|
||
|
||
#: install/index.rst:199
|
||
msgid ""
|
||
"If you don't choose an installation directory---i.e., if you just run "
|
||
"``setup.py install``\\ ---then the :command:`install` command installs to "
|
||
"the standard location for third-party Python modules. This location varies "
|
||
"by platform and by how you built/installed Python itself. On Unix (and Mac "
|
||
"OS X, which is also Unix-based), it also depends on whether the module "
|
||
"distribution being installed is pure Python or contains extensions (\"non-"
|
||
"pure\"):"
|
||
msgstr ""
|
||
"Si vous ne choisissez aucun répertoire d'installation — c'est-à-dire, si "
|
||
"vous lancez simplement ``setup.py install`` — alors la commande :command:"
|
||
"`install` installe le module dans l'emplacement standard pour les modules "
|
||
"tiers de Python. Cet emplacement varie selon la plateforme et selon la façon "
|
||
"dont vous avez construit ou installé Python lui-même. Sous UNIX (et Mac OS "
|
||
"X, qui est également basé sur Unix), cela dépend aussi du module de la "
|
||
"distribution en cours d'installation, suivant qu'il est en pur Python ou "
|
||
"s'il contient des extensions (« non-pur ») :"
|
||
|
||
#: install/index.rst:209
|
||
msgid "Platform"
|
||
msgstr "Plateforme"
|
||
|
||
#: install/index.rst:209
|
||
msgid "Standard installation location"
|
||
msgstr "Emplacement standard de l'installation"
|
||
|
||
#: install/index.rst:209
|
||
msgid "Default value"
|
||
msgstr "Valeur par défaut"
|
||
|
||
#: install/index.rst:735 install/index.rst:747
|
||
msgid "Notes"
|
||
msgstr "Notes"
|
||
|
||
#: install/index.rst:211
|
||
msgid "Unix (pure)"
|
||
msgstr "UNIX (pur)"
|
||
|
||
#: install/index.rst:424
|
||
msgid ":file:`{prefix}/lib/python{X.Y}/site-packages`"
|
||
msgstr ":file:`{prefix}/lib/python{X.Y}/site-packages`"
|
||
|
||
#: install/index.rst:213
|
||
msgid ":file:`/usr/local/lib/python{X.Y}/site-packages`"
|
||
msgstr ":file:`/usr/local/lib/python{X.Y}/site-packages`"
|
||
|
||
#: install/index.rst:213 install/index.rst:737
|
||
msgid "\\(1)"
|
||
msgstr "\\(1)"
|
||
|
||
#: install/index.rst:213
|
||
msgid "Unix (non-pure)"
|
||
msgstr "UNIX (non-pur)"
|
||
|
||
#: install/index.rst:425
|
||
msgid ":file:`{exec-prefix}/lib/python{X.Y}/site-packages`"
|
||
msgstr ":file:`{exec-prefix}/lib/python{X.Y}/site-packages`"
|
||
|
||
#: install/index.rst:215
|
||
msgid "Windows"
|
||
msgstr "Windows"
|
||
|
||
#: install/index.rst:476
|
||
msgid ":file:`{prefix}\\\\Lib\\\\site-packages`"
|
||
msgstr ":file:`{prefix}\\\\Lib\\\\site-packages`"
|
||
|
||
#: install/index.rst:215
|
||
msgid ":file:`C:\\\\Python{XY}\\\\Lib\\\\site-packages`"
|
||
msgstr ":file:`C:\\\\Python{XY}\\\\Lib\\\\site-packages`"
|
||
|
||
#: install/index.rst:739
|
||
msgid "\\(2)"
|
||
msgstr "\\(2)"
|
||
|
||
#: install/index.rst:759
|
||
msgid "Notes:"
|
||
msgstr "Notes :"
|
||
|
||
#: install/index.rst:221
|
||
msgid ""
|
||
"Most Linux distributions include Python as a standard part of the system, "
|
||
"so :file:`{prefix}` and :file:`{exec-prefix}` are usually both :file:`/usr` "
|
||
"on Linux. If you build Python yourself on Linux (or any Unix-like system), "
|
||
"the default :file:`{prefix}` and :file:`{exec-prefix}` are :file:`/usr/"
|
||
"local`."
|
||
msgstr ""
|
||
"La plupart des distributions Linux incluent Python comme un élément de base "
|
||
"du système, donc :file:`{prefix}` et :file:`{exec-prefix}` sont généralement "
|
||
"tous les deux :file:`/usr` sous Linux. Si vous construisez vous-même Python "
|
||
"sous Linux (ou tout autre système de type Unix), les valeurs par défaut de :"
|
||
"file:`{prefix}` et :file:`{exec-prefix}` sont souvent :file:`/usr/local`."
|
||
|
||
#: install/index.rst:227
|
||
msgid ""
|
||
"The default installation directory on Windows was :file:`C:\\\\Program Files"
|
||
"\\\\Python` under Python 1.6a1, 1.5.2, and earlier."
|
||
msgstr ""
|
||
"Sous Windows, le dossier d'installation par défaut était : :file:`C:\\"
|
||
"\\Program Files\\\\Python` sous Python 1.6a1, 1.5.2 et avant."
|
||
|
||
#: install/index.rst:230
|
||
msgid ""
|
||
":file:`{prefix}` and :file:`{exec-prefix}` stand for the directories that "
|
||
"Python is installed to, and where it finds its libraries at run-time. They "
|
||
"are always the same under Windows, and very often the same under Unix and "
|
||
"Mac OS X. You can find out what your Python installation uses for :file:"
|
||
"`{prefix}` and :file:`{exec-prefix}` by running Python in interactive mode "
|
||
"and typing a few simple commands. Under Unix, just type ``python`` at the "
|
||
"shell prompt. Under Windows, choose :menuselection:`Start --> Programs --> "
|
||
"Python X.Y --> Python (command line)`. Once the interpreter is started, "
|
||
"you type Python code at the prompt. For example, on my Linux system, I type "
|
||
"the three Python statements shown below, and get the output as shown, to "
|
||
"find out my :file:`{prefix}` and :file:`{exec-prefix}`:"
|
||
msgstr ""
|
||
":file:`{prefix}` et :file:`{exec-prefix}` désignent les répertoires dans "
|
||
"lesquels Python est installé et où il trouve ses bibliothèques lors de "
|
||
"l'exécution. Ils sont toujours identiques sous Windows et très souvent les "
|
||
"mêmes sous Unix et Mac OS X. Vous pouvez trouver ce que votre installation "
|
||
"de Python utilise pour :file:`{prefix}` et :file:`{exec-prefix}` en "
|
||
"exécutant Python en mode interactif et en tapant quelques commandes simples. "
|
||
"Sous Unix, tapez simplement ``python`` à l'invite du *shell*. Sous Windows, "
|
||
"sélectionnez :menuselection:`Démarrer --> Programmes --> Python X.Y --> "
|
||
"Python (ligne de commande)`. Une fois l'interpréteur démarré, vous tapez du "
|
||
"code Python à l'invite de commande. Par exemple, sur mon système Linux, je "
|
||
"tape les trois instructions ci-dessous et obtiens la sortie suivante pour "
|
||
"trouver mes :file:`{prefix}` et :file:`{exec-prefix}` :"
|
||
|
||
#: install/index.rst:252
|
||
msgid ""
|
||
"A few other placeholders are used in this document: :file:`{X.Y}` stands for "
|
||
"the version of Python, for example ``3.2``; :file:`{abiflags}` will be "
|
||
"replaced by the value of :data:`sys.abiflags` or the empty string for "
|
||
"platforms which don't define ABI flags; :file:`{distname}` will be replaced "
|
||
"by the name of the module distribution being installed. Dots and "
|
||
"capitalization are important in the paths; for example, a value that uses "
|
||
"``python3.2`` on UNIX will typically use ``Python32`` on Windows."
|
||
msgstr ""
|
||
"Quelques autres remplacements utilisés dans ce document : :file:`{X.Y}` "
|
||
"représente la version de Python, par exemple ``3.2`` ; :file:`{abiflags}` "
|
||
"sera remplacé par la valeur de :data:`sys.abiflags` ou la chaine vide pour "
|
||
"les plateformes qui ne définissent pas d’indicateurs d’ABI ; :file:"
|
||
"`{distname}` sera remplacé par le nom de la distribution de modules en train "
|
||
"d’être installée. Les points et la capitalisation sont importantes dans les "
|
||
"chemins ; par exemple, une valeur qui utilise ``python3.2`` sur Unix "
|
||
"utilisera typiquement ``Python32`` sur Windows."
|
||
|
||
#: install/index.rst:260
|
||
msgid ""
|
||
"If you don't want to install modules to the standard location, or if you "
|
||
"don't have permission to write there, then you need to read about alternate "
|
||
"installations in section :ref:`inst-alt-install`. If you want to customize "
|
||
"your installation directories more heavily, see section :ref:`inst-custom-"
|
||
"install` on custom installations."
|
||
msgstr ""
|
||
"Si vous ne voulez pas installer des modules à l'emplacement standard, ou si "
|
||
"vous n'avez pas la permission d'écrire à cet endroit, alors lisez la "
|
||
"section :ref:`inst-alt-install` relative aux installations alternatives. Si "
|
||
"vous souhaitez personnaliser encore plus vos répertoires d'installation, "
|
||
"lisez la section :ref:`inst-custom-install` sur les installations "
|
||
"personnalisées."
|
||
|
||
#: install/index.rst:270
|
||
msgid "Alternate Installation"
|
||
msgstr "Installation alternative"
|
||
|
||
#: install/index.rst:272
|
||
msgid ""
|
||
"Often, it is necessary or desirable to install modules to a location other "
|
||
"than the standard location for third-party Python modules. For example, on "
|
||
"a Unix system you might not have permission to write to the standard third-"
|
||
"party module directory. Or you might wish to try out a module before making "
|
||
"it a standard part of your local Python installation. This is especially "
|
||
"true when upgrading a distribution already present: you want to make sure "
|
||
"your existing base of scripts still works with the new version before "
|
||
"actually upgrading."
|
||
msgstr ""
|
||
"Il est souvent nécessaire ou désirable d’installer des modules à un "
|
||
"emplacement autre que l’emplacement standard pour les modules Python tiers. "
|
||
"Par exemple, sur un système Unix il est possible que vous n’ayez pas la "
|
||
"permission d’écrire dans le dossier standard pour les modules tiers. Ou vous "
|
||
"pouvez vouloir essayer un module avant d’en faire une partie standard de "
|
||
"votre installation locale de Python. C’est surtout vrai lors d’une mise à "
|
||
"jour d’une distribution déjà présente : vous voulez vous assurer que votre "
|
||
"base de scripts fonctionne encore avec la nouvelle version avant de faire la "
|
||
"mise à jour pour de bon."
|
||
|
||
#: install/index.rst:280
|
||
msgid ""
|
||
"The Distutils :command:`install` command is designed to make installing "
|
||
"module distributions to an alternate location simple and painless. The "
|
||
"basic idea is that you supply a base directory for the installation, and "
|
||
"the :command:`install` command picks a set of directories (called an "
|
||
"*installation scheme*) under this base directory in which to install files. "
|
||
"The details differ across platforms, so read whichever of the following "
|
||
"sections applies to you."
|
||
msgstr ""
|
||
"La commande :command:`install` de Distutils est conçue pour rendre "
|
||
"l’installation de distributions de modules à un emplacement alternatif "
|
||
"simple et sans douleur. L’idée de base est que vous lui fournissez un "
|
||
"dossier de base pour l’installation, et la commande :command:`install` "
|
||
"choisit un ensemble de dossiers (appelé le *schéma d’installation*) dans "
|
||
"lequel elle installe les fichiers. Les détails diffèrent d’une plateforme à "
|
||
"une autre, donc lisez les sections ci-dessous qui s’appliquent à vous."
|
||
|
||
#: install/index.rst:288
|
||
msgid ""
|
||
"Note that the various alternate installation schemes are mutually exclusive: "
|
||
"you can pass ``--user``, or ``--home``, or ``--prefix`` and ``--exec-"
|
||
"prefix``, or ``--install-base`` and ``--install-platbase``, but you can't "
|
||
"mix from these groups."
|
||
msgstr ""
|
||
"Notez que les différents schémas d’installation alternative sont "
|
||
"mutuellement exclusifs : vous pouvez passer ``--user``, ou ``--home``, ou "
|
||
"``--prefix`` et ``--exc-prefix``, ou ``--install-base`` et ``--install-"
|
||
"platbase``, mais vous ne pouvez pas mélanger ces groupes."
|
||
|
||
#: install/index.rst:297
|
||
msgid "Alternate installation: the user scheme"
|
||
msgstr "Installation alternative : le schéma *user*"
|
||
|
||
#: install/index.rst:299
|
||
msgid ""
|
||
"This scheme is designed to be the most convenient solution for users that "
|
||
"don't have write permission to the global site-packages directory or don't "
|
||
"want to install into it. It is enabled with a simple option::"
|
||
msgstr ""
|
||
"Ce schéma est conçu pour être la solution la plus pratique pour les "
|
||
"utilisateurs qui n’ont pas la permission d’écrire dans le dossier site-"
|
||
"packages global, ou qui ne veulent pas y écrire. Il est activé avec une "
|
||
"simple option ::"
|
||
|
||
#: install/index.rst:305
|
||
msgid ""
|
||
"Files will be installed into subdirectories of :data:`site.USER_BASE` "
|
||
"(written as :file:`{userbase}` hereafter). This scheme installs pure Python "
|
||
"modules and extension modules in the same location (also known as :data:"
|
||
"`site.USER_SITE`). Here are the values for UNIX, including Mac OS X:"
|
||
msgstr ""
|
||
"Les fichiers seront installés dans des sous-dossiers de :data:`site."
|
||
"USER_BASE` (écrit :file:`{userbase}` dans la suite). Ce schéma installe des "
|
||
"modules Python purs et les modules d’extension au même endroit (aussi connu "
|
||
"sous le nom de :data:`site.USER_SITE`).Voici les valeurs pour UNIX, y "
|
||
"compris Mac OS X ::"
|
||
|
||
#: install/index.rst:322 install/index.rst:422 install/index.rst:499
|
||
#: install/index.rst:747
|
||
msgid "Type of file"
|
||
msgstr "Type de fichier"
|
||
|
||
#: install/index.rst:322 install/index.rst:422 install/index.rst:474
|
||
msgid "Installation directory"
|
||
msgstr "Dossier d'installation"
|
||
|
||
#: install/index.rst:324 install/index.rst:476
|
||
msgid "modules"
|
||
msgstr "modules"
|
||
|
||
#: install/index.rst:313
|
||
msgid ":file:`{userbase}/lib/python{X.Y}/site-packages`"
|
||
msgstr ":file:`{userbase}/lib/python{X.Y}/site-packages`"
|
||
|
||
#: install/index.rst:325 install/index.rst:426 install/index.rst:504
|
||
msgid "scripts"
|
||
msgstr "scripts"
|
||
|
||
#: install/index.rst:314
|
||
msgid ":file:`{userbase}/bin`"
|
||
msgstr ":file:`{userbase}/bin`"
|
||
|
||
#: install/index.rst:326 install/index.rst:427 install/index.rst:505
|
||
msgid "data"
|
||
msgstr "données"
|
||
|
||
#: install/index.rst:326
|
||
msgid ":file:`{userbase}`"
|
||
msgstr ":file:`{userbase}`"
|
||
|
||
#: install/index.rst:327 install/index.rst:428 install/index.rst:506
|
||
msgid "C headers"
|
||
msgstr "en-têtes C"
|
||
|
||
#: install/index.rst:316
|
||
msgid ":file:`{userbase}/include/python{X.Y}{abiflags}/{distname}`"
|
||
msgstr ":file:`{userbase}/include/python{X.Y}{abiflags}/{distname}`"
|
||
|
||
#: install/index.rst:319
|
||
msgid "And here are the values used on Windows:"
|
||
msgstr "Et voici les valeurs utilisées sur Windows ::"
|
||
|
||
#: install/index.rst:324
|
||
msgid ":file:`{userbase}\\\\Python{XY}\\\\site-packages`"
|
||
msgstr ":file:`{userbase}\\\\Python{XY}\\\\site-packages`"
|
||
|
||
#: install/index.rst:325
|
||
msgid ":file:`{userbase}\\\\Python{XY}\\\\Scripts`"
|
||
msgstr ":file:`{userbase}\\\\Python{XY}\\\\Scripts`"
|
||
|
||
#: install/index.rst:327
|
||
msgid ":file:`{userbase}\\\\Python{XY}\\\\Include\\\\{distname}`"
|
||
msgstr ":file:`{userbase}\\\\Python{XY}\\\\Include\\\\{distname}`"
|
||
|
||
#: install/index.rst:330
|
||
msgid ""
|
||
"The advantage of using this scheme compared to the other ones described "
|
||
"below is that the user site-packages directory is under normal conditions "
|
||
"always included in :data:`sys.path` (see :mod:`site` for more information), "
|
||
"which means that there is no additional step to perform after running the :"
|
||
"file:`setup.py` script to finalize the installation."
|
||
msgstr ""
|
||
"L’avantage d’utiliser ce schéma plutôt que les autres décrits plus bas est "
|
||
"que le dossier site-package du schéma *user* est en temps normal toujours "
|
||
"inclus dans :data:`sys.path` (voir :mod:`site` pour plus d’informations), ce "
|
||
"qui signifie qu’il n’y a rien d’autre à faire après avoir exécuté le script :"
|
||
"file:`setup.py` pour finaliser l’installation."
|
||
|
||
#: install/index.rst:336
|
||
msgid ""
|
||
"The :command:`build_ext` command also has a ``--user`` option to add :file:"
|
||
"`{userbase}/include` to the compiler search path for header files and :file:"
|
||
"`{userbase}/lib` to the compiler search path for libraries as well as to the "
|
||
"runtime search path for shared C libraries (rpath)."
|
||
msgstr ""
|
||
"La commande :command:`build_ext` possède aussi une option ``--user`` pour "
|
||
"ajouter :file:`{userbase}/include` dans les chemins où le compilateur "
|
||
"recherche les fichiers d'en-têtes et :file:`{userbase}/lib` dans les chemins "
|
||
"où le compilateur recherche les bibliothèques ainsi que les bibliothèques C "
|
||
"partagées chargeables à l'exécution (`rpath`)."
|
||
|
||
#: install/index.rst:345
|
||
msgid "Alternate installation: the home scheme"
|
||
msgstr "Installation alternative : le schéma *home*"
|
||
|
||
#: install/index.rst:347
|
||
msgid ""
|
||
"The idea behind the \"home scheme\" is that you build and maintain a "
|
||
"personal stash of Python modules. This scheme's name is derived from the "
|
||
"idea of a \"home\" directory on Unix, since it's not unusual for a Unix user "
|
||
"to make their home directory have a layout similar to :file:`/usr/` or :file:"
|
||
"`/usr/local/`. This scheme can be used by anyone, regardless of the "
|
||
"operating system they are installing for."
|
||
msgstr ""
|
||
"L’idée derrière le « schéma home » est que vous compilez et maintenez un "
|
||
"espace personnel de modules Python. Le nom de ce schéma vient de l’idée du "
|
||
"dossier « home » sur Unix, vu qu’il n’est pas rare pour un utilisateur UNIX "
|
||
"d'agencer son dossier *home* avec la même disposition que :file:`/usr/` ou :"
|
||
"file:`/usr/local/`. Ce schéma peut être utilisé par n’importe qui, quel que "
|
||
"soit le système d’exploitation."
|
||
|
||
#: install/index.rst:354
|
||
msgid "Installing a new module distribution is as simple as ::"
|
||
msgstr "Installer une nouvelle distribution de module est aussi simple que ::"
|
||
|
||
#: install/index.rst:358
|
||
msgid ""
|
||
"where you can supply any directory you like for the :option:`!--home` "
|
||
"option. On Unix, lazy typists can just type a tilde (``~``); the :command:"
|
||
"`install` command will expand this to your home directory::"
|
||
msgstr ""
|
||
"où vous pouvez fournir le dossier de votre choix à l’option :option:`!--"
|
||
"home`. Sur Unix, les paresseux peuvent mettre un simple tilde (``~``) ; la "
|
||
"commande :command:`install` le remplacera par le chemin vers votre dossier "
|
||
"personnel ::"
|
||
|
||
#: install/index.rst:364
|
||
msgid ""
|
||
"To make Python find the distributions installed with this scheme, you may "
|
||
"have to :ref:`modify Python's search path <inst-search-path>` or edit :mod:"
|
||
"`sitecustomize` (see :mod:`site`) to call :func:`site.addsitedir` or edit :"
|
||
"data:`sys.path`."
|
||
msgstr ""
|
||
"Pour que Python puisse trouver les distributions installées avec ce schéma, "
|
||
"vous devez :ref:`modifier le chemin de recherche de Python <inst-search-"
|
||
"path>` ou modifier :mod:`sitecustomize` (voir :mod:`site`) pour appeler :"
|
||
"func:`site.addsitedir` ou modifier :data:`sys.path`."
|
||
|
||
#: install/index.rst:369
|
||
msgid ""
|
||
"The :option:`!--home` option defines the installation base directory. Files "
|
||
"are installed to the following directories under the installation base as "
|
||
"follows:"
|
||
msgstr ""
|
||
"L’option :option:`!--home` définit le dossier de base de l’installation. Les "
|
||
"fichiers sont installés dans les dossiers suivants sous la base de "
|
||
"l'installation de la façon suivante ::"
|
||
|
||
#: install/index.rst:375
|
||
msgid ":file:`{home}/lib/python`"
|
||
msgstr ":file:`{home}/lib/python`"
|
||
|
||
#: install/index.rst:376
|
||
msgid ":file:`{home}/bin`"
|
||
msgstr ":file:`{home}/bin`"
|
||
|
||
#: install/index.rst:377
|
||
msgid ":file:`{home}`"
|
||
msgstr ":file:`{home}`"
|
||
|
||
#: install/index.rst:378
|
||
msgid ":file:`{home}/include/python/{distname}`"
|
||
msgstr ":file:`{home}/include/python/{distname}`"
|
||
|
||
#: install/index.rst:381
|
||
msgid "(Mentally replace slashes with backslashes if you're on Windows.)"
|
||
msgstr ""
|
||
"(Remplacez mentalement les slashs avec des antislashs si vous êtes sur "
|
||
"Windows.)"
|
||
|
||
#: install/index.rst:387
|
||
msgid "Alternate installation: Unix (the prefix scheme)"
|
||
msgstr "Installation alternative : Unix (le schéma de préfixe)"
|
||
|
||
#: install/index.rst:389
|
||
msgid ""
|
||
"The \"prefix scheme\" is useful when you wish to use one Python installation "
|
||
"to perform the build/install (i.e., to run the setup script), but install "
|
||
"modules into the third-party module directory of a different Python "
|
||
"installation (or something that looks like a different Python "
|
||
"installation). If this sounds a trifle unusual, it is---that's why the user "
|
||
"and home schemes come before. However, there are at least two known cases "
|
||
"where the prefix scheme will be useful."
|
||
msgstr ""
|
||
"Le schéma de préfixe est utile quand vous voulez une installation de Python "
|
||
"pour faire la compilation/l’installation (c.-à-d. exécuter le script "
|
||
"*setup*), mais utiliser les modules tiers d’une installation Python "
|
||
"différente (ou quelque chose qui ressemble à une installation Python "
|
||
"différente). Si cela vous semble inhabituel, ça l’est — c’est pourquoi les "
|
||
"schémas *user* et *home* viennent avant. Cependant, il y a au moins deux cas "
|
||
"connus où le schéma *prefix* est utile."
|
||
|
||
#: install/index.rst:396
|
||
msgid ""
|
||
"First, consider that many Linux distributions put Python in :file:`/usr`, "
|
||
"rather than the more traditional :file:`/usr/local`. This is entirely "
|
||
"appropriate, since in those cases Python is part of \"the system\" rather "
|
||
"than a local add-on. However, if you are installing Python modules from "
|
||
"source, you probably want them to go in :file:`/usr/local/lib/python2.{X}` "
|
||
"rather than :file:`/usr/lib/python2.{X}`. This can be done with ::"
|
||
msgstr ""
|
||
"Premièrement, considérez que beaucoup de distributions Linux mettent Python "
|
||
"dans :file:`/usr`, plutôt que le traditionnel :file:`/usr/local`. C’est tout "
|
||
"à fait approprié, puisque dans ces cas Python fait partie du « système » "
|
||
"plutôt que d’une addition locale. Cependant, si vous installez des modules "
|
||
"Python depuis leur source, vous voulez probablement qu’ils aillent dans :"
|
||
"file:`/usr/local/lib/python2.{X}` plutôt que dans :file:`/usr/lib/python2.{X}"
|
||
"`. Ça peut être fait avec ::"
|
||
|
||
#: install/index.rst:405
|
||
msgid ""
|
||
"Another possibility is a network filesystem where the name used to write to "
|
||
"a remote directory is different from the name used to read it: for example, "
|
||
"the Python interpreter accessed as :file:`/usr/local/bin/python` might "
|
||
"search for modules in :file:`/usr/local/lib/python2.{X}`, but those modules "
|
||
"would have to be installed to, say, :file:`/mnt/{@server}/export/lib/python2."
|
||
"{X}`. This could be done with ::"
|
||
msgstr ""
|
||
"Une autre possibilité est un système de fichiers réseau où le nom utilisé "
|
||
"pour écrire dans un dossier distant est différent du nom utilisé pour le "
|
||
"lire : par exemple, l’interpréteur Python auquel on accède par :file:`/usr/"
|
||
"local/bin/python` peut chercher les modules dans :file:`/usr/local/lib/"
|
||
"python2.{X}`, mais ces modules doivent être installés dans, par exemple, :"
|
||
"file:`/mnt/{@server}/export/lib/python2.{X}`. Ça peut être fait avec ::"
|
||
|
||
#: install/index.rst:414
|
||
msgid ""
|
||
"In either case, the :option:`!--prefix` option defines the installation "
|
||
"base, and the :option:`!--exec-prefix` option defines the platform-specific "
|
||
"installation base, which is used for platform-specific files. (Currently, "
|
||
"this just means non-pure module distributions, but could be expanded to C "
|
||
"libraries, binary executables, etc.) If :option:`!--exec-prefix` is not "
|
||
"supplied, it defaults to :option:`!--prefix`. Files are installed as "
|
||
"follows:"
|
||
msgstr ""
|
||
"Dans les deux cas, l’option :option:`!--prefix` définit la base de "
|
||
"l’installation et l’option :option:`!--exec-prefix` définit la base "
|
||
"d’installation spécifique à la plateforme, qui est utilisée pour des "
|
||
"fichiers spécifiques à la plateforme (actuellement, ça ne concerne que les "
|
||
"distributions de modules non-purs, mais cela pourrait être étendu aux "
|
||
"bibliothèques C, exécutables, etc.). Si l'option :option:`!--exec-prefix` "
|
||
"n’est pas fournie, elle vaut par défaut :option:`!--prefix`. Les fichiers "
|
||
"sont installés ainsi :"
|
||
|
||
#: install/index.rst:501
|
||
msgid "Python modules"
|
||
msgstr "Modules Python"
|
||
|
||
#: install/index.rst:502
|
||
msgid "extension modules"
|
||
msgstr "modules d'extension"
|
||
|
||
#: install/index.rst:426
|
||
msgid ":file:`{prefix}/bin`"
|
||
msgstr ":file:`{prefix}/bin`"
|
||
|
||
#: install/index.rst:478
|
||
msgid ":file:`{prefix}`"
|
||
msgstr ":file:`{prefix}`"
|
||
|
||
#: install/index.rst:428
|
||
msgid ":file:`{prefix}/include/python{X.Y}{abiflags}/{distname}`"
|
||
msgstr ":file:`{prefix}/include/python{X.Y}{abiflags}/{distname}`"
|
||
|
||
#: install/index.rst:431
|
||
msgid ""
|
||
"There is no requirement that :option:`!--prefix` or :option:`!--exec-prefix` "
|
||
"actually point to an alternate Python installation; if the directories "
|
||
"listed above do not already exist, they are created at installation time."
|
||
msgstr ""
|
||
"Il n'est pas obligatoire que :option:`!--prefix` ou :option:`!--exec-prefix` "
|
||
"pointent vers une installation alternative de Python. Si les dossiers listés "
|
||
"ci-dessus n’existent pas, ils sont créés au moment de l’installation."
|
||
|
||
#: install/index.rst:435
|
||
msgid ""
|
||
"Incidentally, the real reason the prefix scheme is important is simply that "
|
||
"a standard Unix installation uses the prefix scheme, but with :option:`!--"
|
||
"prefix` and :option:`!--exec-prefix` supplied by Python itself as ``sys."
|
||
"prefix`` and ``sys.exec_prefix``. Thus, you might think you'll never use "
|
||
"the prefix scheme, but every time you run ``python setup.py install`` "
|
||
"without any other options, you're using it."
|
||
msgstr ""
|
||
"Accessoirement, la vraie raison pour laquelle le schéma *prefix* est "
|
||
"important est simplement qu’une installation Unix standard utilise le schéma "
|
||
"*prefix*, mais avec les options :option:`!--prefix` et :option:`!--exec-"
|
||
"prefix` fournies par Python lui-même en tant que ``sys.prefix`` et ``sys."
|
||
"exec_prefix``. Vous pouvez donc penser que vous n’utiliserez jamais le "
|
||
"schéma *prefix*, mais à chaque fois que vous lancez ``python setup.py "
|
||
"install`` sans autre option, vous l’utilisez."
|
||
|
||
#: install/index.rst:442
|
||
msgid ""
|
||
"Note that installing extensions to an alternate Python installation has no "
|
||
"effect on how those extensions are built: in particular, the Python header "
|
||
"files (:file:`Python.h` and friends) installed with the Python interpreter "
|
||
"used to run the setup script will be used in compiling extensions. It is "
|
||
"your responsibility to ensure that the interpreter used to run extensions "
|
||
"installed in this way is compatible with the interpreter used to build "
|
||
"them. The best way to do this is to ensure that the two interpreters are "
|
||
"the same version of Python (possibly different builds, or possibly copies of "
|
||
"the same build). (Of course, if your :option:`!--prefix` and :option:`!--"
|
||
"exec-prefix` don't even point to an alternate Python installation, this is "
|
||
"immaterial.)"
|
||
msgstr ""
|
||
"Notez qu’installer des extensions à une installation Python alternative n’a "
|
||
"aucun effet sur la façon dont ces extensions sont construites. En "
|
||
"particulier, les fichiers en-têtes de Python (:file:`Python.h` et ses amis) "
|
||
"installés avec l’interpréteur Python utilisé pour exécuter le script *setup* "
|
||
"seront utilisés pour compiler les extensions. Il est de votre responsabilité "
|
||
"de vous assurer que l’interpréteur utilisé pour exécuter les extensions "
|
||
"installées de cette façon est compatible avec celui utilisé pour les "
|
||
"compiler. La meilleure façon pour cela est de s’assurer qu’ils sont "
|
||
"exactement la même version de Python (possiblement des compilations "
|
||
"différentes, ou différentes copies de la même). (Évidemment, si vos :option:"
|
||
"`!--prefix` et :option:`!--exec-prefix` ne pointent pas vers une "
|
||
"installation alternative de Python, cela n’a pas de sens.)"
|
||
|
||
#: install/index.rst:457
|
||
msgid "Alternate installation: Windows (the prefix scheme)"
|
||
msgstr "Installation alternative : Windows (le schéma de préfixe)"
|
||
|
||
#: install/index.rst:459
|
||
msgid ""
|
||
"Windows has no concept of a user's home directory, and since the standard "
|
||
"Python installation under Windows is simpler than under Unix, the :option:"
|
||
"`!--prefix` option has traditionally been used to install additional "
|
||
"packages in separate locations on Windows. ::"
|
||
msgstr ""
|
||
"Windows n'a pas de concept de répertoire utilisateur, et comme "
|
||
"l'installation standard de Python sur Windows est plus simple que sur Unix, "
|
||
"l':option:`!--prefix` option a traditionnellement été utilisée pour "
|
||
"installer des paquets supplémentaires à des endroits séparés sur Windows. ::"
|
||
|
||
#: install/index.rst:466
|
||
msgid ""
|
||
"to install modules to the :file:`\\\\Temp\\\\Python` directory on the "
|
||
"current drive."
|
||
msgstr ""
|
||
"pour installer des modules dans le dossier :file:`\\\\Temp\\\\Python` du "
|
||
"disque courant."
|
||
|
||
#: install/index.rst:468
|
||
msgid ""
|
||
"The installation base is defined by the :option:`!--prefix` option; the :"
|
||
"option:`!--exec-prefix` option is not supported under Windows, which means "
|
||
"that pure Python modules and extension modules are installed into the same "
|
||
"location. Files are installed as follows:"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:477
|
||
msgid ":file:`{prefix}\\\\Scripts`"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:479
|
||
msgid ":file:`{prefix}\\\\Include\\\\{distname}`"
|
||
msgstr ":file:`{prefix}\\\\Include\\\\{distname}`"
|
||
|
||
#: install/index.rst:486
|
||
msgid "Custom Installation"
|
||
msgstr "Installation personnalisée"
|
||
|
||
#: install/index.rst:488
|
||
msgid ""
|
||
"Sometimes, the alternate installation schemes described in section :ref:"
|
||
"`inst-alt-install` just don't do what you want. You might want to tweak "
|
||
"just one or two directories while keeping everything under the same base "
|
||
"directory, or you might want to completely redefine the installation "
|
||
"scheme. In either case, you're creating a *custom installation scheme*."
|
||
msgstr ""
|
||
"Parfois, les procédés d'installation alternatifs décrits dans la section :"
|
||
"ref:`inst-alt-install` ne font pas ce que vous attendiez. Vous pourriez "
|
||
"vouloir modifier seulement un ou deux répertoires en conservant tout le "
|
||
"reste sous la même racine, ou vouloir redéfinir l'ensemble du procédé "
|
||
"d'installation. Quel que soit le cas, vous créez ainsi un *procédé "
|
||
"d'installation personnalisé*."
|
||
|
||
#: install/index.rst:494
|
||
msgid ""
|
||
"To create a custom installation scheme, you start with one of the alternate "
|
||
"schemes and override some of the installation directories used for the "
|
||
"various types of files, using these options:"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:499
|
||
msgid "Override option"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:501
|
||
msgid "``--install-purelib``"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:502
|
||
msgid "``--install-platlib``"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:503
|
||
msgid "all modules"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:503
|
||
msgid "``--install-lib``"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:504
|
||
msgid "``--install-scripts``"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:505
|
||
msgid "``--install-data``"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:506
|
||
msgid "``--install-headers``"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:509
|
||
msgid ""
|
||
"These override options can be relative, absolute, or explicitly defined in "
|
||
"terms of one of the installation base directories. (There are two "
|
||
"installation base directories, and they are normally the same---they only "
|
||
"differ when you use the Unix \"prefix scheme\" and supply different ``--"
|
||
"prefix`` and ``--exec-prefix`` options; using ``--install-lib`` will "
|
||
"override values computed or given for ``--install-purelib`` and ``--install-"
|
||
"platlib``, and is recommended for schemes that don't make a difference "
|
||
"between Python and extension modules.)"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:518
|
||
msgid ""
|
||
"For example, say you're installing a module distribution to your home "
|
||
"directory under Unix---but you want scripts to go in :file:`~/scripts` "
|
||
"rather than :file:`~/bin`. As you might expect, you can override this "
|
||
"directory with the :option:`!--install-scripts` option; in this case, it "
|
||
"makes most sense to supply a relative path, which will be interpreted "
|
||
"relative to the installation base directory (your home directory, in this "
|
||
"case)::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:527
|
||
msgid ""
|
||
"Another Unix example: suppose your Python installation was built and "
|
||
"installed with a prefix of :file:`/usr/local/python`, so under a standard "
|
||
"installation scripts will wind up in :file:`/usr/local/python/bin`. If you "
|
||
"want them in :file:`/usr/local/bin` instead, you would supply this absolute "
|
||
"directory for the :option:`!--install-scripts` option::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:535
|
||
msgid ""
|
||
"(This performs an installation using the \"prefix scheme\", where the prefix "
|
||
"is whatever your Python interpreter was installed with--- :file:`/usr/local/"
|
||
"python` in this case.)"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:539
|
||
msgid ""
|
||
"If you maintain Python on Windows, you might want third-party modules to "
|
||
"live in a subdirectory of :file:`{prefix}`, rather than right in :file:"
|
||
"`{prefix}` itself. This is almost as easy as customizing the script "
|
||
"installation directory---you just have to remember that there are two types "
|
||
"of modules to worry about, Python and extension modules, which can "
|
||
"conveniently be both controlled by one option::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:548
|
||
msgid ""
|
||
"The specified installation directory is relative to :file:`{prefix}`. Of "
|
||
"course, you also have to ensure that this directory is in Python's module "
|
||
"search path, such as by putting a :file:`.pth` file in a site directory "
|
||
"(see :mod:`site`). See section :ref:`inst-search-path` to find out how to "
|
||
"modify Python's search path."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:554
|
||
msgid ""
|
||
"If you want to define an entire installation scheme, you just have to supply "
|
||
"all of the installation directory options. The recommended way to do this "
|
||
"is to supply relative paths; for example, if you want to maintain all Python "
|
||
"module-related files under :file:`python` in your home directory, and you "
|
||
"want a separate directory for each platform that you use your home directory "
|
||
"from, you might define the following installation scheme::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:567
|
||
msgid "or, equivalently, ::"
|
||
msgstr "ou ::"
|
||
|
||
#: install/index.rst:575
|
||
msgid ""
|
||
"``$PLAT`` is not (necessarily) an environment variable---it will be expanded "
|
||
"by the Distutils as it parses your command line options, just as it does "
|
||
"when parsing your configuration file(s)."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:579
|
||
msgid ""
|
||
"Obviously, specifying the entire installation scheme every time you install "
|
||
"a new module distribution would be very tedious. Thus, you can put these "
|
||
"options into your Distutils config file (see section :ref:`inst-config-"
|
||
"files`):"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:592
|
||
msgid "or, equivalently,"
|
||
msgstr "ou (équivalent),"
|
||
|
||
#: install/index.rst:603
|
||
msgid ""
|
||
"Note that these two are *not* equivalent if you supply a different "
|
||
"installation base directory when you run the setup script. For example, ::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:608
|
||
msgid ""
|
||
"would install pure modules to :file:`/tmp/python/lib` in the first case, and "
|
||
"to :file:`/tmp/lib` in the second case. (For the second case, you probably "
|
||
"want to supply an installation base of :file:`/tmp/python`.)"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:612
|
||
msgid ""
|
||
"You probably noticed the use of ``$HOME`` and ``$PLAT`` in the sample "
|
||
"configuration file input. These are Distutils configuration variables, "
|
||
"which bear a strong resemblance to environment variables. In fact, you can "
|
||
"use environment variables in config files on platforms that have such a "
|
||
"notion but the Distutils additionally define a few extra variables that may "
|
||
"not be in your environment, such as ``$PLAT``. (And of course, on systems "
|
||
"that don't have environment variables, such as Mac OS 9, the configuration "
|
||
"variables supplied by the Distutils are the only ones you can use.) See "
|
||
"section :ref:`inst-config-files` for details."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:622
|
||
msgid ""
|
||
"When a :ref:`virtual environment <venv-def>` is activated, any options that "
|
||
"change the installation path will be ignored from all distutils "
|
||
"configuration files to prevent inadvertently installing projects outside of "
|
||
"the virtual environment."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:636
|
||
msgid "Modifying Python's Search Path"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:638
|
||
msgid ""
|
||
"When the Python interpreter executes an :keyword:`import` statement, it "
|
||
"searches for both Python code and extension modules along a search path. A "
|
||
"default value for the path is configured into the Python binary when the "
|
||
"interpreter is built. You can determine the path by importing the :mod:`sys` "
|
||
"module and printing the value of ``sys.path``. ::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:655
|
||
msgid ""
|
||
"The null string in ``sys.path`` represents the current working directory."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:657
|
||
msgid ""
|
||
"The expected convention for locally installed packages is to put them in "
|
||
"the :file:`{...}/site-packages/` directory, but you may want to install "
|
||
"Python modules into some arbitrary directory. For example, your site may "
|
||
"have a convention of keeping all software related to the web server under :"
|
||
"file:`/www`. Add-on Python modules might then belong in :file:`/www/python`, "
|
||
"and in order to import them, this directory must be added to ``sys.path``. "
|
||
"There are several different ways to add the directory."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:665
|
||
msgid ""
|
||
"The most convenient way is to add a path configuration file to a directory "
|
||
"that's already on Python's path, usually to the :file:`.../site-packages/` "
|
||
"directory. Path configuration files have an extension of :file:`.pth`, and "
|
||
"each line must contain a single path that will be appended to ``sys.path``. "
|
||
"(Because the new paths are appended to ``sys.path``, modules in the added "
|
||
"directories will not override standard modules. This means you can't use "
|
||
"this mechanism for installing fixed versions of standard modules.)"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:673
|
||
msgid ""
|
||
"Paths can be absolute or relative, in which case they're relative to the "
|
||
"directory containing the :file:`.pth` file. See the documentation of the :"
|
||
"mod:`site` module for more information."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:677
|
||
msgid ""
|
||
"A slightly less convenient way is to edit the :file:`site.py` file in "
|
||
"Python's standard library, and modify ``sys.path``. :file:`site.py` is "
|
||
"automatically imported when the Python interpreter is executed, unless the :"
|
||
"option:`-S` switch is supplied to suppress this behaviour. So you could "
|
||
"simply edit :file:`site.py` and add two lines to it:"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:688
|
||
msgid ""
|
||
"However, if you reinstall the same major version of Python (perhaps when "
|
||
"upgrading from 2.2 to 2.2.2, for example) :file:`site.py` will be "
|
||
"overwritten by the stock version. You'd have to remember that it was "
|
||
"modified and save a copy before doing the installation."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:693
|
||
msgid ""
|
||
"There are two environment variables that can modify ``sys.path``. :envvar:"
|
||
"`PYTHONHOME` sets an alternate value for the prefix of the Python "
|
||
"installation. For example, if :envvar:`PYTHONHOME` is set to ``/www/"
|
||
"python``, the search path will be set to ``['', '/www/python/lib/pythonX."
|
||
"Y/', '/www/python/lib/pythonX.Y/plat-linux2', ...]``."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:699
|
||
msgid ""
|
||
"The :envvar:`PYTHONPATH` variable can be set to a list of paths that will be "
|
||
"added to the beginning of ``sys.path``. For example, if :envvar:"
|
||
"`PYTHONPATH` is set to ``/www/python:/opt/py``, the search path will begin "
|
||
"with ``['/www/python', '/opt/py']``. (Note that directories must exist in "
|
||
"order to be added to ``sys.path``; the :mod:`site` module removes paths that "
|
||
"don't exist.)"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:706
|
||
msgid ""
|
||
"Finally, ``sys.path`` is just a regular Python list, so any Python "
|
||
"application can modify it by adding or removing entries."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:713
|
||
msgid "Distutils Configuration Files"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:715
|
||
msgid ""
|
||
"As mentioned above, you can use Distutils configuration files to record "
|
||
"personal or site preferences for any Distutils options. That is, any option "
|
||
"to any command can be stored in one of two or three (depending on your "
|
||
"platform) configuration files, which will be consulted before the command-"
|
||
"line is parsed. This means that configuration files will override default "
|
||
"values, and the command-line will in turn override configuration files. "
|
||
"Furthermore, if multiple configuration files apply, values from \"earlier\" "
|
||
"files are overridden by \"later\" files."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:728
|
||
msgid "Location and names of config files"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:730
|
||
msgid ""
|
||
"The names and locations of the configuration files vary slightly across "
|
||
"platforms. On Unix and Mac OS X, the three configuration files (in the "
|
||
"order they are processed) are:"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:747
|
||
msgid "Location and filename"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:749
|
||
msgid "system"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:737
|
||
msgid ":file:`{prefix}/lib/python{ver}/distutils/distutils.cfg`"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:751
|
||
msgid "personal"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:739
|
||
msgid ":file:`$HOME/.pydistutils.cfg`"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:753
|
||
msgid "local"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:753
|
||
msgid ":file:`setup.cfg`"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:753
|
||
msgid "\\(3)"
|
||
msgstr "\\(3)"
|
||
|
||
#: install/index.rst:744
|
||
msgid "And on Windows, the configuration files are:"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:749
|
||
msgid ":file:`{prefix}\\\\Lib\\\\distutils\\\\distutils.cfg`"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:749
|
||
msgid "\\(4)"
|
||
msgstr "\\(4)"
|
||
|
||
#: install/index.rst:751
|
||
msgid ":file:`%HOME%\\\\pydistutils.cfg`"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:751
|
||
msgid "\\(5)"
|
||
msgstr "\\(5)"
|
||
|
||
#: install/index.rst:756
|
||
msgid ""
|
||
"On all platforms, the \"personal\" file can be temporarily disabled by "
|
||
"passing the `--no-user-cfg` option."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:762
|
||
msgid ""
|
||
"Strictly speaking, the system-wide configuration file lives in the directory "
|
||
"where the Distutils are installed; under Python 1.6 and later on Unix, this "
|
||
"is as shown. For Python 1.5.2, the Distutils will normally be installed to :"
|
||
"file:`{prefix}/lib/python1.5/site-packages/distutils`, so the system "
|
||
"configuration file should be put there under Python 1.5.2."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:769
|
||
msgid ""
|
||
"On Unix, if the :envvar:`HOME` environment variable is not defined, the "
|
||
"user's home directory will be determined with the :func:`getpwuid` function "
|
||
"from the standard :mod:`pwd` module. This is done by the :func:`os.path."
|
||
"expanduser` function used by Distutils."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:775
|
||
msgid ""
|
||
"I.e., in the current directory (usually the location of the setup script)."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:778
|
||
msgid ""
|
||
"(See also note (1).) Under Python 1.6 and later, Python's default "
|
||
"\"installation prefix\" is :file:`C:\\\\Python`, so the system configuration "
|
||
"file is normally :file:`C:\\\\Python\\\\Lib\\\\distutils\\\\distutils.cfg`. "
|
||
"Under Python 1.5.2, the default prefix was :file:`C:\\\\Program Files\\"
|
||
"\\Python`, and the Distutils were not part of the standard library---so the "
|
||
"system configuration file would be :file:`C:\\\\Program Files\\\\Python\\"
|
||
"\\distutils\\\\distutils.cfg` in a standard Python 1.5.2 installation under "
|
||
"Windows."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:787
|
||
msgid ""
|
||
"On Windows, if the :envvar:`HOME` environment variable is not defined, :"
|
||
"envvar:`USERPROFILE` then :envvar:`HOMEDRIVE` and :envvar:`HOMEPATH` will be "
|
||
"tried. This is done by the :func:`os.path.expanduser` function used by "
|
||
"Distutils."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:796
|
||
msgid "Syntax of config files"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:798
|
||
msgid ""
|
||
"The Distutils configuration files all have the same syntax. The config "
|
||
"files are grouped into sections. There is one section for each Distutils "
|
||
"command, plus a ``global`` section for global options that affect every "
|
||
"command. Each section consists of one option per line, specified as "
|
||
"``option=value``."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:803
|
||
msgid ""
|
||
"For example, the following is a complete config file that just forces all "
|
||
"commands to run quietly by default:"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:811
|
||
msgid ""
|
||
"If this is installed as the system config file, it will affect all "
|
||
"processing of any Python module distribution by any user on the current "
|
||
"system. If it is installed as your personal config file (on systems that "
|
||
"support them), it will affect only module distributions processed by you. "
|
||
"And if it is used as the :file:`setup.cfg` for a particular module "
|
||
"distribution, it affects only that distribution."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:818
|
||
msgid ""
|
||
"You could override the default \"build base\" directory and make the :"
|
||
"command:`build\\*` commands always forcibly rebuild all files with the "
|
||
"following:"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:828
|
||
msgid "which corresponds to the command-line arguments ::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:832
|
||
msgid ""
|
||
"except that including the :command:`build` command on the command-line means "
|
||
"that command will be run. Including a particular command in config files "
|
||
"has no such implication; it only means that if the command is run, the "
|
||
"options in the config file will apply. (Or if other commands that derive "
|
||
"values from it are run, they will use the values in the config file.)"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:838
|
||
msgid ""
|
||
"You can find out the complete list of options for any command using the :"
|
||
"option:`!--help` option, e.g.::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:843
|
||
msgid ""
|
||
"and you can find out the complete list of global options by using :option:"
|
||
"`!--help` without a command::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:848
|
||
msgid ""
|
||
"See also the \"Reference\" section of the \"Distributing Python Modules\" "
|
||
"manual."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:854
|
||
msgid "Building Extensions: Tips and Tricks"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:856
|
||
msgid ""
|
||
"Whenever possible, the Distutils try to use the configuration information "
|
||
"made available by the Python interpreter used to run the :file:`setup.py` "
|
||
"script. For example, the same compiler and linker flags used to compile "
|
||
"Python will also be used for compiling extensions. Usually this will work "
|
||
"well, but in complicated situations this might be inappropriate. This "
|
||
"section discusses how to override the usual Distutils behaviour."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:867
|
||
msgid "Tweaking compiler/linker flags"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:869
|
||
msgid ""
|
||
"Compiling a Python extension written in C or C++ will sometimes require "
|
||
"specifying custom flags for the compiler and linker in order to use a "
|
||
"particular library or produce a special kind of object code. This is "
|
||
"especially true if the extension hasn't been tested on your platform, or if "
|
||
"you're trying to cross-compile Python."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:875
|
||
msgid ""
|
||
"In the most general case, the extension author might have foreseen that "
|
||
"compiling the extensions would be complicated, and provided a :file:`Setup` "
|
||
"file for you to edit. This will likely only be done if the module "
|
||
"distribution contains many separate extension modules, or if they often "
|
||
"require elaborate sets of compiler flags in order to work."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:881
|
||
msgid ""
|
||
"A :file:`Setup` file, if present, is parsed in order to get a list of "
|
||
"extensions to build. Each line in a :file:`Setup` describes a single "
|
||
"module. Lines have the following structure::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:888
|
||
msgid "Let's examine each of the fields in turn."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:890
|
||
msgid ""
|
||
"*module* is the name of the extension module to be built, and should be a "
|
||
"valid Python identifier. You can't just change this in order to rename a "
|
||
"module (edits to the source code would also be needed), so this should be "
|
||
"left alone."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:894
|
||
msgid ""
|
||
"*sourcefile* is anything that's likely to be a source code file, at least "
|
||
"judging by the filename. Filenames ending in :file:`.c` are assumed to be "
|
||
"written in C, filenames ending in :file:`.C`, :file:`.cc`, and :file:`.c++` "
|
||
"are assumed to be C++, and filenames ending in :file:`.m` or :file:`.mm` are "
|
||
"assumed to be in Objective C."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:900
|
||
msgid ""
|
||
"*cpparg* is an argument for the C preprocessor, and is anything starting "
|
||
"with :option:`!-I`, :option:`!-D`, :option:`!-U` or :option:`!-C`."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:903
|
||
msgid ""
|
||
"*library* is anything ending in :file:`.a` or beginning with :option:`!-l` "
|
||
"or :option:`!-L`."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:906
|
||
msgid ""
|
||
"If a particular platform requires a special library on your platform, you "
|
||
"can add it by editing the :file:`Setup` file and running ``python setup.py "
|
||
"build``. For example, if the module defined by the line ::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:912
|
||
msgid ""
|
||
"must be linked with the math library :file:`libm.a` on your platform, simply "
|
||
"add :option:`!-lm` to the line::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:917
|
||
msgid ""
|
||
"Arbitrary switches intended for the compiler or the linker can be supplied "
|
||
"with the :option:`!-Xcompiler` *arg* and :option:`!-Xlinker` *arg* options::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:922
|
||
msgid ""
|
||
"The next option after :option:`!-Xcompiler` and :option:`!-Xlinker` will be "
|
||
"appended to the proper command line, so in the above example the compiler "
|
||
"will be passed the :option:`!-o32` option, and the linker will be passed :"
|
||
"option:`!-shared`. If a compiler option requires an argument, you'll have "
|
||
"to supply multiple :option:`!-Xcompiler` options; for example, to pass ``-x c"
|
||
"++`` the :file:`Setup` file would have to contain ``-Xcompiler -x -Xcompiler "
|
||
"c++``."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:929
|
||
msgid ""
|
||
"Compiler flags can also be supplied through setting the :envvar:`CFLAGS` "
|
||
"environment variable. If set, the contents of :envvar:`CFLAGS` will be "
|
||
"added to the compiler flags specified in the :file:`Setup` file."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:937
|
||
msgid "Using non-Microsoft compilers on Windows"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:944
|
||
msgid "Borland/CodeGear C++"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:946
|
||
msgid ""
|
||
"This subsection describes the necessary steps to use Distutils with the "
|
||
"Borland C++ compiler version 5.5. First you have to know that Borland's "
|
||
"object file format (OMF) is different from the format used by the Python "
|
||
"version you can download from the Python or ActiveState Web site. (Python "
|
||
"is built with Microsoft Visual C++, which uses COFF as the object file "
|
||
"format.) For this reason you have to convert Python's library :file:"
|
||
"`python25.lib` into the Borland format. You can do this as follows:"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:961
|
||
msgid ""
|
||
"The :file:`coff2omf` program comes with the Borland compiler. The file :"
|
||
"file:`python25.lib` is in the :file:`Libs` directory of your Python "
|
||
"installation. If your extension uses other libraries (zlib, ...) you have "
|
||
"to convert them too."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:966
|
||
msgid ""
|
||
"The converted files have to reside in the same directories as the normal "
|
||
"libraries."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:969
|
||
msgid ""
|
||
"How does Distutils manage to use these libraries with their changed names? "
|
||
"If the extension needs a library (eg. :file:`foo`) Distutils checks first if "
|
||
"it finds a library with suffix :file:`_bcpp` (eg. :file:`foo_bcpp.lib`) and "
|
||
"then uses this library. In the case it doesn't find such a special library "
|
||
"it uses the default name (:file:`foo.lib`.) [#]_"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:975
|
||
msgid ""
|
||
"To let Distutils compile your extension with Borland C++ you now have to "
|
||
"type::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:979
|
||
msgid ""
|
||
"If you want to use the Borland C++ compiler as the default, you could "
|
||
"specify this in your personal or system-wide configuration file for "
|
||
"Distutils (see section :ref:`inst-config-files`.)"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:988
|
||
msgid "`C++Builder Compiler <https://www.embarcadero.com/products>`_"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:987
|
||
msgid ""
|
||
"Information about the free C++ compiler from Borland, including links to the "
|
||
"download pages."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:991
|
||
msgid ""
|
||
"`Creating Python Extensions Using Borland's Free Compiler <http://www."
|
||
"cyberus.ca/~g_will/pyExtenDL.shtml>`_"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:991
|
||
msgid ""
|
||
"Document describing how to use Borland's free command-line C++ compiler to "
|
||
"build Python."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:996
|
||
msgid "GNU C / Cygwin / MinGW"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:998
|
||
msgid ""
|
||
"This section describes the necessary steps to use Distutils with the GNU C/C+"
|
||
"+ compilers in their Cygwin and MinGW distributions. [#]_ For a Python "
|
||
"interpreter that was built with Cygwin, everything should work without any "
|
||
"of these following steps."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:1003
|
||
msgid ""
|
||
"Not all extensions can be built with MinGW or Cygwin, but many can. "
|
||
"Extensions most likely to not work are those that use C++ or depend on "
|
||
"Microsoft Visual C extensions."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:1007
|
||
msgid "To let Distutils compile your extension with Cygwin you have to type::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:1011
|
||
msgid "and for Cygwin in no-cygwin mode [#]_ or for MinGW type::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:1015
|
||
msgid ""
|
||
"If you want to use any of these options/compilers as default, you should "
|
||
"consider writing it in your personal or system-wide configuration file for "
|
||
"Distutils (see section :ref:`inst-config-files`.)"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:1020
|
||
msgid "Older Versions of Python and MinGW"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:1021
|
||
msgid ""
|
||
"The following instructions only apply if you're using a version of Python "
|
||
"inferior to 2.4.1 with a MinGW inferior to 3.0.0 (with "
|
||
"binutils-2.13.90-20030111-1)."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:1025
|
||
msgid ""
|
||
"These compilers require some special libraries. This task is more complex "
|
||
"than for Borland's C++, because there is no program to convert the library. "
|
||
"First you have to create a list of symbols which the Python DLL exports. "
|
||
"(You can find a good program for this task at https://sourceforge.net/"
|
||
"projects/mingw/files/MinGW/Extension/pexports/)."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:1038
|
||
msgid ""
|
||
"The location of an installed :file:`python25.dll` will depend on the "
|
||
"installation options and the version and language of Windows. In a \"just "
|
||
"for me\" installation, it will appear in the root of the installation "
|
||
"directory. In a shared installation, it will be located in the system "
|
||
"directory."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:1043
|
||
msgid ""
|
||
"Then you can create from these information an import library for gcc. ::"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:1047
|
||
msgid ""
|
||
"The resulting library has to be placed in the same directory as :file:"
|
||
"`python25.lib`. (Should be the :file:`libs` directory under your Python "
|
||
"installation directory.)"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:1051
|
||
msgid ""
|
||
"If your extension uses other libraries (zlib,...) you might have to convert "
|
||
"them too. The converted files have to reside in the same directories as the "
|
||
"normal libraries do."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:1058
|
||
msgid ""
|
||
"`Building Python modules on MS Windows platform with MinGW <http://old.zope."
|
||
"org/Members/als/tips/win32_mingw_modules>`_"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:1059
|
||
msgid ""
|
||
"Information about building the required libraries for the MinGW environment."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:1063
|
||
msgid "Footnotes"
|
||
msgstr "Notes"
|
||
|
||
#: install/index.rst:1064
|
||
msgid ""
|
||
"This also means you could replace all existing COFF-libraries with OMF-"
|
||
"libraries of the same name."
|
||
msgstr ""
|
||
|
||
#: install/index.rst:1067
|
||
msgid ""
|
||
"Check https://www.sourceware.org/cygwin/ and http://www.mingw.org/ for more "
|
||
"information"
|
||
msgstr ""
|
||
|
||
#: install/index.rst:1070
|
||
msgid ""
|
||
"Then you have no POSIX emulation available, but you also don't need :file:"
|
||
"`cygwin1.dll`."
|
||
msgstr ""
|