forked from AFPy/python-docs-fr
203 lines
6.6 KiB
Plaintext
203 lines
6.6 KiB
Plaintext
# SOME DESCRIPTIVE TITLE.
|
|
# Copyright (C) 1990-2016, Python Software Foundation
|
|
# This file is distributed under the same license as the Python package.
|
|
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
|
|
#
|
|
#, fuzzy
|
|
msgid ""
|
|
msgstr ""
|
|
"Project-Id-Version: Python 2.7\n"
|
|
"Report-Msgid-Bugs-To: \n"
|
|
"POT-Creation-Date: 2016-10-30 10:44+0100\n"
|
|
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
|
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
|
"Language-Team: LANGUAGE <LL@li.org>\n"
|
|
"MIME-Version: 1.0\n"
|
|
"Content-Type: text/plain; charset=UTF-8\n"
|
|
"Content-Transfer-Encoding: 8bit\n"
|
|
|
|
#: ../Doc/distutils/examples.rst:5
|
|
msgid "Examples"
|
|
msgstr "Exemples"
|
|
|
|
#: ../Doc/distutils/examples.rst:7
|
|
msgid ""
|
|
"This chapter provides a number of basic examples to help get started with "
|
|
"distutils. Additional information about using distutils can be found in the "
|
|
"Distutils Cookbook."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:14
|
|
msgid "`Distutils Cookbook <https://wiki.python.org/moin/Distutils/Cookbook>`_"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:15
|
|
msgid ""
|
|
"Collection of recipes showing how to achieve more control over distutils."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:21
|
|
msgid "Pure Python distribution (by module)"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:23
|
|
msgid ""
|
|
"If you're just distributing a couple of modules, especially if they don't "
|
|
"live in a particular package, you can specify them individually using the "
|
|
"``py_modules`` option in the setup script."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:27
|
|
msgid ""
|
|
"In the simplest case, you'll have two files to worry about: a setup script "
|
|
"and the single module you're distributing, :file:`foo.py` in this example::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:34
|
|
msgid ""
|
|
"(In all diagrams in this section, *<root>* will refer to the distribution "
|
|
"root directory.) A minimal setup script to describe this situation would "
|
|
"be::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:43
|
|
msgid ""
|
|
"Note that the name of the distribution is specified independently with the "
|
|
"``name`` option, and there's no rule that says it has to be the same as the "
|
|
"name of the sole module in the distribution (although that's probably a good "
|
|
"convention to follow). However, the distribution name is used to generate "
|
|
"filenames, so you should stick to letters, digits, underscores, and hyphens."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:49
|
|
msgid ""
|
|
"Since ``py_modules`` is a list, you can of course specify multiple modules, "
|
|
"eg. if you're distributing modules :mod:`foo` and :mod:`bar`, your setup "
|
|
"might look like this::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:58
|
|
msgid "and the setup script might be ::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:66
|
|
msgid ""
|
|
"You can put module source files into another directory, but if you have "
|
|
"enough modules to do that, it's probably easier to specify modules by "
|
|
"package rather than listing them individually."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:74
|
|
msgid "Pure Python distribution (by package)"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:76
|
|
msgid ""
|
|
"If you have more than a couple of modules to distribute, especially if they "
|
|
"are in multiple packages, it's probably easier to specify whole packages "
|
|
"rather than individual modules. This works even if your modules are not in "
|
|
"a package; you can just tell the Distutils to process modules from the root "
|
|
"package, and that works the same as any other package (except that you don't "
|
|
"have to have an :file:`__init__.py` file)."
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:83
|
|
msgid "The setup script from the last example could also be written as ::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:91
|
|
msgid "(The empty string stands for the root package.)"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:93
|
|
msgid ""
|
|
"If those two files are moved into a subdirectory, but remain in the root "
|
|
"package, e.g.::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:101
|
|
msgid ""
|
|
"then you would still specify the root package, but you have to tell the "
|
|
"Distutils where source files in the root package live::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:111
|
|
msgid ""
|
|
"More typically, though, you will want to distribute multiple modules in the "
|
|
"same package (or in sub-packages). For example, if the :mod:`foo` and :mod:"
|
|
"`bar` modules belong in package :mod:`foobar`, one way to layout your source "
|
|
"tree is ::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:123
|
|
msgid ""
|
|
"This is in fact the default layout expected by the Distutils, and the one "
|
|
"that requires the least work to describe in your setup script::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:132
|
|
msgid ""
|
|
"If you want to put modules in directories not named for their package, then "
|
|
"you need to use the ``package_dir`` option again. For example, if the :file:"
|
|
"`src` directory holds modules in the :mod:`foobar` package::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:143
|
|
msgid "an appropriate setup script would be ::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:152
|
|
msgid ""
|
|
"Or, you might put modules from your main package right in the distribution "
|
|
"root::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:161
|
|
msgid "in which case your setup script would be ::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:170
|
|
msgid "(The empty string also stands for the current directory.)"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:172
|
|
msgid ""
|
|
"If you have sub-packages, they must be explicitly listed in ``packages``, "
|
|
"but any entries in ``package_dir`` automatically extend to sub-packages. (In "
|
|
"other words, the Distutils does *not* scan your source tree, trying to "
|
|
"figure out which directories correspond to Python packages by looking for :"
|
|
"file:`__init__.py` files.) Thus, if the default layout grows a sub-package::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:188
|
|
msgid "then the corresponding setup script would be ::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:200
|
|
msgid "Single extension module"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:202
|
|
msgid ""
|
|
"Extension modules are specified using the ``ext_modules`` option. "
|
|
"``package_dir`` has no effect on where extension source files are found; it "
|
|
"only affects the source for pure Python modules. The simplest case, a "
|
|
"single extension module in a single C source file, is::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:211
|
|
msgid ""
|
|
"If the :mod:`foo` extension belongs in the root package, the setup script "
|
|
"for this could be ::"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:221
|
|
msgid "If the extension actually belongs in a package, say :mod:`foopkg`, then"
|
|
msgstr ""
|
|
|
|
#: ../Doc/distutils/examples.rst:223
|
|
msgid ""
|
|
"With exactly the same source tree layout, this extension can be put in the :"
|
|
"mod:`foopkg` package simply by changing the name of the extension::"
|
|
msgstr ""
|