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

3.6: merge pot files

Browse source
This commit is contained in:
Julien Palard 2017-04-02 22:14:06 +02:00
commit a25cddd031
463 changed files with 31928 additions and 26519 deletions
Download patch file Download diff file Expand all files Collapse all files

71
install/index.po
View file

@ -8,10 +8,11 @@ msgid ""
msgstr ""
"Project-Id-Version: Python 3.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-10-30 10:40+0100\n"
"POT-Creation-Date: 2017-04-02 22:11+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
@ -332,12 +333,13 @@ msgid "How building works"
msgstr "Comment fonctionne une construction"
#: ../Doc/install/index.rst:200
#, fuzzy
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::"
"directory with the :option:`!--build-base` option. For example::"
msgstr ""
"Comme sous-entendu ci-dessus, la commande :command:`build` est chargé de "
"mettre les fichiers à installer dans un *répertoire de travail*. Par défaut, "
@ -781,8 +783,9 @@ msgstr ""
"Installer une nouvelle distribution de module est aussi simple que : ::"
#: ../Doc/install/index.rst:402
#, fuzzy
msgid ""
"where you can supply any directory you like for the :option:`--home` "
"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 ""
@ -804,8 +807,9 @@ msgstr ""
"func:`site.addsitedir` ou modifiez :data:`sys.path`."
#: ../Doc/install/index.rst:413
#, fuzzy
msgid ""
"The :option:`--home` option defines the installation base directory. Files "
"The :option:`!--home` option defines the installation base directory. Files "
"are installed to the following directories under the installation base as "
"follows:"
msgstr ""
@ -891,13 +895,15 @@ msgstr ""
"export/lib/python2.{X}`.Ça peut être fait avec : ::"
#: ../Doc/install/index.rst:458
#, fuzzy
msgid ""
"In either case, the :option:`--prefix` option defines the installation base, "
"and the :option:`--exec-prefix` option defines the platform-specific "
"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:"
"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 "
@ -928,8 +934,9 @@ msgid ":file:`{prefix}/include/python{X.Y}{abiflags}/{distname}`"
msgstr ":file:`{prefix}/include/python{X.Y}{abiflags}/{distname}`"
#: ../Doc/install/index.rst:475
#, fuzzy
msgid ""
"There is no requirement that :option:`--prefix` or :option:`--exec-prefix` "
"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 ""
@ -938,10 +945,11 @@ msgstr ""
"ci-dessus n’existent pas, ils sont créés au moment de l’installation."
#: ../Doc/install/index.rst:479
#, fuzzy
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."
"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."
@ -955,6 +963,7 @@ msgstr ""
"install`` sans autre option, vous l’utilisez."
#: ../Doc/install/index.rst:486
#, fuzzy
msgid ""
"Note that installing extensions to an alternate Python installation has no "
"effect on how those extensions are built: in particular, the Python header "
@ -964,8 +973,8 @@ msgid ""
"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 "
"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 "
@ -988,9 +997,9 @@ msgstr ""
#: ../Doc/install/index.rst:503
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. ::"
"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 ""
#: ../Doc/install/index.rst:510
@ -1001,8 +1010,8 @@ msgstr ""
#: ../Doc/install/index.rst:512
msgid ""
"The installation base is defined by the :option:`--prefix` option; the :"
"option:`--exec-prefix` option is not supported under Windows, which means "
"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 ""
@ -1084,7 +1093,7 @@ 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 "
"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)::"
@ -1096,7 +1105,7 @@ msgid ""
"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::"
"directory for the :option:`!--install-scripts` option::"
msgstr ""
#: ../Doc/install/index.rst:579
@ -1538,13 +1547,13 @@ msgstr ""
#: ../Doc/install/index.rst:934
msgid ""
"*cpparg* is an argument for the C preprocessor, and is anything starting "
"with :option:`!-I`, :option:`-D`, :option:`!-U` or :option:`-C`."
"with :option:`!-I`, :option:`!-D`, :option:`!-U` or :option:`!-C`."
msgstr ""
#: ../Doc/install/index.rst:937
msgid ""
"*library* is anything ending in :file:`.a` or beginning with :option:`-l` "
"or :option:`-L`."
"*library* is anything ending in :file:`.a` or beginning with :option:`!-l` "
"or :option:`!-L`."
msgstr ""
#: ../Doc/install/index.rst:940
@ -1557,24 +1566,24 @@ msgstr ""
#: ../Doc/install/index.rst:946
msgid ""
"must be linked with the math library :file:`libm.a` on your platform, simply "
"add :option:`-lm` to the line::"
"add :option:`!-lm` to the line::"
msgstr ""
#: ../Doc/install/index.rst:951
msgid ""
"Arbitrary switches intended for the compiler or the linker can be supplied "
"with the :option:`-Xcompiler` *arg* and :option:`-Xlinker` *arg* options::"
"with the :option:`!-Xcompiler` *arg* and :option:`!-Xlinker` *arg* options::"
msgstr ""
#: ../Doc/install/index.rst:956
msgid ""
"The next option after :option:`-Xcompiler` and :option:`-Xlinker` will be "
"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"
"++``."
"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 ""
#: ../Doc/install/index.rst:963