# SOME DESCRIPTIVE TITLE. # Copyright (C) 2001-2016, Python Software Foundation # This file is distributed under the same license as the Python package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Python 3.6\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2016-10-30 10:40+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../Doc/distutils/builtdist.rst:5 msgid "Creating Built Distributions" msgstr "" #: ../Doc/distutils/builtdist.rst:7 msgid "" "A \"built distribution\" is what you're probably used to thinking of either " "as a \"binary package\" or an \"installer\" (depending on your background). " "It's not necessarily binary, though, because it might contain only Python " "source code and/or byte-code; and we don't call it a package, because that " "word is already spoken for in Python. (And \"installer\" is a term specific " "to the world of mainstream desktop systems.)" msgstr "" #: ../Doc/distutils/builtdist.rst:14 msgid "" "A built distribution is how you make life as easy as possible for installers " "of your module distribution: for users of RPM-based Linux systems, it's a " "binary RPM; for Windows users, it's an executable installer; for Debian-" "based Linux users, it's a Debian package; and so forth. Obviously, no one " "person will be able to create built distributions for every platform under " "the sun, so the Distutils are designed to enable module developers to " "concentrate on their specialty---writing code and creating source " "distributions---while an intermediary species called *packagers* springs up " "to turn source distributions into built distributions for as many platforms " "as there are packagers." msgstr "" #: ../Doc/distutils/builtdist.rst:24 msgid "" "Of course, the module developer could be his own packager; or the packager " "could be a volunteer \"out there\" somewhere who has access to a platform " "which the original developer does not; or it could be software periodically " "grabbing new source distributions and turning them into built distributions " "for as many platforms as the software has access to. Regardless of who they " "are, a packager uses the setup script and the :command:`bdist` command " "family to generate built distributions." msgstr "" #: ../Doc/distutils/builtdist.rst:32 msgid "" "As a simple example, if I run the following command in the Distutils source " "tree::" msgstr "" #: ../Doc/distutils/builtdist.rst:37 msgid "" "then the Distutils builds my module distribution (the Distutils itself in " "this case), does a \"fake\" installation (also in the :file:`build` " "directory), and creates the default type of built distribution for my " "platform. The default format for built distributions is a \"dumb\" tar file " "on Unix, and a simple executable installer on Windows. (That tar file is " "considered \"dumb\" because it has to be unpacked in a specific location to " "work.)" msgstr "" #: ../Doc/distutils/builtdist.rst:44 msgid "" "Thus, the above command on a Unix system creates :file:`Distutils-1.0.{plat}." "tar.gz`; unpacking this tarball from the right place installs the Distutils " "just as though you had downloaded the source distribution and run ``python " "setup.py install``. (The \"right place\" is either the root of the " "filesystem or Python's :file:`{prefix}` directory, depending on the options " "given to the :command:`bdist_dumb` command; the default is to make dumb " "distributions relative to :file:`{prefix}`.)" msgstr "" #: ../Doc/distutils/builtdist.rst:52 msgid "" "Obviously, for pure Python distributions, this isn't any simpler than just " "running ``python setup.py install``\\ ---but for non-pure distributions, " "which include extensions that would need to be compiled, it can mean the " "difference between someone being able to use your extensions or not. And " "creating \"smart\" built distributions, such as an RPM package or an " "executable installer for Windows, is far more convenient for users even if " "your distribution doesn't include any extensions." msgstr "" #: ../Doc/distutils/builtdist.rst:60 msgid "" "The :command:`bdist` command has a :option:`--formats` option, similar to " "the :command:`sdist` command, which you can use to select the types of built " "distribution to generate: for example, ::" msgstr "" #: ../Doc/distutils/builtdist.rst:66 msgid "" "would, when run on a Unix system, create :file:`Distutils-1.0.{plat}.zip`\\ " "---again, this archive would be unpacked from the root directory to install " "the Distutils." msgstr "" #: ../Doc/distutils/builtdist.rst:70 msgid "The available formats for built distributions are:" msgstr "" #: ../Doc/distutils/builtdist.rst:73 msgid "Format" msgstr "Format" #: ../Doc/distutils/builtdist.rst:73 msgid "Description" msgstr "Description" #: ../Doc/distutils/builtdist.rst:73 msgid "Notes" msgstr "Notes" #: ../Doc/distutils/builtdist.rst:75 msgid "``gztar``" msgstr "" #: ../Doc/distutils/builtdist.rst:75 msgid "gzipped tar file (:file:`.tar.gz`)" msgstr "" #: ../Doc/distutils/builtdist.rst:75 msgid "\\(1)" msgstr "\\(1)" #: ../Doc/distutils/builtdist.rst:78 msgid "``bztar``" msgstr "" #: ../Doc/distutils/builtdist.rst:78 msgid "bzipped tar file (:file:`.tar.bz2`)" msgstr "" #: ../Doc/distutils/builtdist.rst:81 msgid "``xztar``" msgstr "" #: ../Doc/distutils/builtdist.rst:81 msgid "xzipped tar file (:file:`.tar.xz`)" msgstr "" #: ../Doc/distutils/builtdist.rst:84 msgid "``ztar``" msgstr "" #: ../Doc/distutils/builtdist.rst:84 msgid "compressed tar file (:file:`.tar.Z`)" msgstr "" #: ../Doc/distutils/builtdist.rst:84 msgid "\\(3)" msgstr "\\(3)" #: ../Doc/distutils/builtdist.rst:87 msgid "``tar``" msgstr "" #: ../Doc/distutils/builtdist.rst:87 msgid "tar file (:file:`.tar`)" msgstr "" #: ../Doc/distutils/builtdist.rst:89 msgid "``zip``" msgstr "" #: ../Doc/distutils/builtdist.rst:89 msgid "zip file (:file:`.zip`)" msgstr "" #: ../Doc/distutils/builtdist.rst:89 msgid "(2),(4)" msgstr "" #: ../Doc/distutils/builtdist.rst:91 msgid "``rpm``" msgstr "" #: ../Doc/distutils/builtdist.rst:91 msgid "RPM" msgstr "" #: ../Doc/distutils/builtdist.rst:91 msgid "\\(5)" msgstr "\\(5)" #: ../Doc/distutils/builtdist.rst:93 msgid "``pkgtool``" msgstr "" #: ../Doc/distutils/builtdist.rst:93 msgid "Solaris :program:`pkgtool`" msgstr "" #: ../Doc/distutils/builtdist.rst:95 msgid "``sdux``" msgstr "" #: ../Doc/distutils/builtdist.rst:95 msgid "HP-UX :program:`swinstall`" msgstr "" #: ../Doc/distutils/builtdist.rst:97 msgid "``wininst``" msgstr "" #: ../Doc/distutils/builtdist.rst:97 msgid "self-extracting ZIP file for Windows" msgstr "" #: ../Doc/distutils/builtdist.rst:97 msgid "\\(4)" msgstr "\\(4)" #: ../Doc/distutils/builtdist.rst:100 msgid "``msi``" msgstr "" #: ../Doc/distutils/builtdist.rst:100 msgid "Microsoft Installer." msgstr "" #: ../Doc/distutils/builtdist.rst:103 msgid "Added support for the ``xztar`` format." msgstr "" #: ../Doc/distutils/builtdist.rst:107 msgid "Notes:" msgstr "Notes : " #: ../Doc/distutils/builtdist.rst:110 msgid "default on Unix" msgstr "" #: ../Doc/distutils/builtdist.rst:113 msgid "default on Windows" msgstr "" #: ../Doc/distutils/builtdist.rst:116 msgid "requires external :program:`compress` utility." msgstr "" #: ../Doc/distutils/builtdist.rst:119 msgid "" "requires either external :program:`zip` utility or :mod:`zipfile` module " "(part of the standard Python library since Python 1.6)" msgstr "" #: ../Doc/distutils/builtdist.rst:123 msgid "" "requires external :program:`rpm` utility, version 3.0.4 or better (use ``rpm " "--version`` to find out which version you have)" msgstr "" #: ../Doc/distutils/builtdist.rst:126 msgid "" "You don't have to use the :command:`bdist` command with the :option:`--" "formats` option; you can also use the command that directly implements the " "format you're interested in. Some of these :command:`bdist` \"sub-commands" "\" actually generate several similar formats; for instance, the :command:" "`bdist_dumb` command generates all the \"dumb\" archive formats (``tar``, " "``gztar``, ``bztar``, ``xztar``, ``ztar``, and ``zip``), and :command:" "`bdist_rpm` generates both binary and source RPMs. The :command:`bdist` sub-" "commands, and the formats generated by each, are:" msgstr "" #: ../Doc/distutils/builtdist.rst:136 msgid "Command" msgstr "" #: ../Doc/distutils/builtdist.rst:136 msgid "Formats" msgstr "Formats" #: ../Doc/distutils/builtdist.rst:138 msgid ":command:`bdist_dumb`" msgstr "" #: ../Doc/distutils/builtdist.rst:138 msgid "tar, gztar, bztar, xztar, ztar, zip" msgstr "" #: ../Doc/distutils/builtdist.rst:140 msgid ":command:`bdist_rpm`" msgstr "" #: ../Doc/distutils/builtdist.rst:140 msgid "rpm, srpm" msgstr "" #: ../Doc/distutils/builtdist.rst:142 msgid ":command:`bdist_wininst`" msgstr "" #: ../Doc/distutils/builtdist.rst:142 msgid "wininst" msgstr "" #: ../Doc/distutils/builtdist.rst:144 msgid ":command:`bdist_msi`" msgstr "" #: ../Doc/distutils/builtdist.rst:144 msgid "msi" msgstr "" #: ../Doc/distutils/builtdist.rst:147 msgid "" "The following sections give details on the individual :command:`bdist_\\*` " "commands." msgstr "" #: ../Doc/distutils/builtdist.rst:163 msgid "Creating RPM packages" msgstr "" #: ../Doc/distutils/builtdist.rst:165 msgid "" "The RPM format is used by many popular Linux distributions, including Red " "Hat, SuSE, and Mandrake. If one of these (or any of the other RPM-based " "Linux distributions) is your usual environment, creating RPM packages for " "other users of that same distribution is trivial. Depending on the " "complexity of your module distribution and differences between Linux " "distributions, you may also be able to create RPMs that work on different " "RPM-based distributions." msgstr "" #: ../Doc/distutils/builtdist.rst:172 msgid "" "The usual way to create an RPM of your module distribution is to run the :" "command:`bdist_rpm` command::" msgstr "" #: ../Doc/distutils/builtdist.rst:177 msgid "or the :command:`bdist` command with the :option:`--format` option::" msgstr "" #: ../Doc/distutils/builtdist.rst:181 msgid "" "The former allows you to specify RPM-specific options; the latter allows " "you to easily specify multiple formats in one run. If you need to do both, " "you can explicitly specify multiple :command:`bdist_\\*` commands and their " "options::" msgstr "" #: ../Doc/distutils/builtdist.rst:188 msgid "" "Creating RPM packages is driven by a :file:`.spec` file, much as using the " "Distutils is driven by the setup script. To make your life easier, the :" "command:`bdist_rpm` command normally creates a :file:`.spec` file based on " "the information you supply in the setup script, on the command line, and in " "any Distutils configuration files. Various options and sections in the :" "file:`.spec` file are derived from options in the setup script as follows:" msgstr "" #: ../Doc/distutils/builtdist.rst:196 ../Doc/distutils/builtdist.rst:220 msgid "RPM :file:`.spec` file option or section" msgstr "" #: ../Doc/distutils/builtdist.rst:196 msgid "Distutils setup script option" msgstr "" #: ../Doc/distutils/builtdist.rst:198 msgid "Name" msgstr "Nom" #: ../Doc/distutils/builtdist.rst:198 msgid "``name``" msgstr "" #: ../Doc/distutils/builtdist.rst:200 msgid "Summary (in preamble)" msgstr "" #: ../Doc/distutils/builtdist.rst:200 msgid "``description``" msgstr "" #: ../Doc/distutils/builtdist.rst:202 msgid "Version" msgstr "" #: ../Doc/distutils/builtdist.rst:202 msgid "``version``" msgstr "``version``" #: ../Doc/distutils/builtdist.rst:204 ../Doc/distutils/builtdist.rst:227 msgid "Vendor" msgstr "" #: ../Doc/distutils/builtdist.rst:204 msgid "" "``author`` and ``author_email``, or --- & ``maintainer`` and " "``maintainer_email``" msgstr "" #: ../Doc/distutils/builtdist.rst:208 msgid "Copyright" msgstr "Copyright" #: ../Doc/distutils/builtdist.rst:208 msgid "``license``" msgstr "" #: ../Doc/distutils/builtdist.rst:210 msgid "Url" msgstr "" #: ../Doc/distutils/builtdist.rst:210 msgid "``url``" msgstr "" #: ../Doc/distutils/builtdist.rst:212 msgid "%description (section)" msgstr "" #: ../Doc/distutils/builtdist.rst:212 msgid "``long_description``" msgstr "" #: ../Doc/distutils/builtdist.rst:215 msgid "" "Additionally, there are many options in :file:`.spec` files that don't have " "corresponding options in the setup script. Most of these are handled " "through options to the :command:`bdist_rpm` command as follows:" msgstr "" #: ../Doc/distutils/builtdist.rst:220 msgid ":command:`bdist_rpm` option" msgstr "" #: ../Doc/distutils/builtdist.rst:220 msgid "default value" msgstr "" #: ../Doc/distutils/builtdist.rst:223 msgid "Release" msgstr "Version" #: ../Doc/distutils/builtdist.rst:223 msgid "``release``" msgstr "" #: ../Doc/distutils/builtdist.rst:223 msgid "\"1\"" msgstr "" #: ../Doc/distutils/builtdist.rst:225 msgid "Group" msgstr "" #: ../Doc/distutils/builtdist.rst:225 msgid "``group``" msgstr "" #: ../Doc/distutils/builtdist.rst:225 msgid "\"Development/Libraries\"" msgstr "" #: ../Doc/distutils/builtdist.rst:227 msgid "``vendor``" msgstr "" #: ../Doc/distutils/builtdist.rst:227 msgid "(see above)" msgstr "" #: ../Doc/distutils/builtdist.rst:229 msgid "Packager" msgstr "" #: ../Doc/distutils/builtdist.rst:229 msgid "``packager``" msgstr "``packager``" #: ../Doc/distutils/builtdist.rst:229 ../Doc/distutils/builtdist.rst:231 #: ../Doc/distutils/builtdist.rst:233 ../Doc/distutils/builtdist.rst:235 #: ../Doc/distutils/builtdist.rst:237 ../Doc/distutils/builtdist.rst:239 #: ../Doc/distutils/builtdist.rst:241 ../Doc/distutils/builtdist.rst:243 msgid "(none)" msgstr "" #: ../Doc/distutils/builtdist.rst:231 msgid "Provides" msgstr "" #: ../Doc/distutils/builtdist.rst:231 msgid "``provides``" msgstr "" #: ../Doc/distutils/builtdist.rst:233 msgid "Requires" msgstr "" #: ../Doc/distutils/builtdist.rst:233 msgid "``requires``" msgstr "" #: ../Doc/distutils/builtdist.rst:235 msgid "Conflicts" msgstr "" #: ../Doc/distutils/builtdist.rst:235 msgid "``conflicts``" msgstr "" #: ../Doc/distutils/builtdist.rst:237 msgid "Obsoletes" msgstr "" #: ../Doc/distutils/builtdist.rst:237 msgid "``obsoletes``" msgstr "" #: ../Doc/distutils/builtdist.rst:239 msgid "Distribution" msgstr "" #: ../Doc/distutils/builtdist.rst:239 msgid "``distribution_name``" msgstr "``distribution_name``" #: ../Doc/distutils/builtdist.rst:241 msgid "BuildRequires" msgstr "" #: ../Doc/distutils/builtdist.rst:241 msgid "``build_requires``" msgstr "" #: ../Doc/distutils/builtdist.rst:243 msgid "Icon" msgstr "" #: ../Doc/distutils/builtdist.rst:243 msgid "``icon``" msgstr "" #: ../Doc/distutils/builtdist.rst:246 msgid "" "Obviously, supplying even a few of these options on the command-line would " "be tedious and error-prone, so it's usually best to put them in the setup " "configuration file, :file:`setup.cfg`\\ ---see section :ref:`setup-config`. " "If you distribute or package many Python module distributions, you might " "want to put options that apply to all of them in your personal Distutils " "configuration file (:file:`~/.pydistutils.cfg`). If you want to temporarily " "disable this file, you can pass the :option:`--no-user-cfg` option to :file:" "`setup.py`." msgstr "" #: ../Doc/distutils/builtdist.rst:254 msgid "" "There are three steps to building a binary RPM package, all of which are " "handled automatically by the Distutils:" msgstr "" #: ../Doc/distutils/builtdist.rst:257 msgid "" "create a :file:`.spec` file, which describes the package (analogous to the " "Distutils setup script; in fact, much of the information in the setup " "script winds up in the :file:`.spec` file)" msgstr "" #: ../Doc/distutils/builtdist.rst:261 msgid "create the source RPM" msgstr "" #: ../Doc/distutils/builtdist.rst:263 msgid "" "create the \"binary\" RPM (which may or may not contain binary code, " "depending on whether your module distribution contains Python extensions)" msgstr "" #: ../Doc/distutils/builtdist.rst:266 msgid "" "Normally, RPM bundles the last two steps together; when you use the " "Distutils, all three steps are typically bundled together." msgstr "" #: ../Doc/distutils/builtdist.rst:269 msgid "" "If you wish, you can separate these three steps. You can use the :option:`--" "spec-only` option to make :command:`bdist_rpm` just create the :file:`.spec` " "file and exit; in this case, the :file:`.spec` file will be written to the " "\"distribution directory\"---normally :file:`dist/`, but customizable with " "the :option:`--dist-dir` option. (Normally, the :file:`.spec` file winds up " "deep in the \"build tree,\" in a temporary directory created by :command:" "`bdist_rpm`.)" msgstr "" #: ../Doc/distutils/builtdist.rst:297 msgid "Creating Windows Installers" msgstr "" #: ../Doc/distutils/builtdist.rst:299 msgid "" "Executable installers are the natural format for binary distributions on " "Windows. They display a nice graphical user interface, display some " "information about the module distribution to be installed taken from the " "metadata in the setup script, let the user select a few options, and start " "or cancel the installation." msgstr "" #: ../Doc/distutils/builtdist.rst:305 msgid "" "Since the metadata is taken from the setup script, creating Windows " "installers is usually as easy as running::" msgstr "" #: ../Doc/distutils/builtdist.rst:310 msgid "or the :command:`bdist` command with the :option:`--formats` option::" msgstr "" #: ../Doc/distutils/builtdist.rst:314 msgid "" "If you have a pure module distribution (only containing pure Python modules " "and packages), the resulting installer will be version independent and have " "a name like :file:`foo-1.0.win32.exe`. These installers can even be created " "on Unix platforms or Mac OS X." msgstr "" #: ../Doc/distutils/builtdist.rst:319 msgid "" "If you have a non-pure distribution, the extensions can only be created on a " "Windows platform, and will be Python version dependent. The installer " "filename will reflect this and now has the form :file:`foo-1.0.win32-py2.0." "exe`. You have to create a separate installer for every Python version you " "want to support." msgstr "" #: ../Doc/distutils/builtdist.rst:325 msgid "" "The installer will try to compile pure modules into :term:`bytecode` after " "installation on the target system in normal and optimizing mode. If you " "don't want this to happen for some reason, you can run the :command:" "`bdist_wininst` command with the :option:`--no-target-compile` and/or the :" "option:`--no-target-optimize` option." msgstr "" #: ../Doc/distutils/builtdist.rst:331 msgid "" "By default the installer will display the cool \"Python Powered\" logo when " "it is run, but you can also supply your own 152x261 bitmap which must be a " "Windows :file:`.bmp` file with the :option:`--bitmap` option." msgstr "" #: ../Doc/distutils/builtdist.rst:335 msgid "" "The installer will also display a large title on the desktop background " "window when it is run, which is constructed from the name of your " "distribution and the version number. This can be changed to another text by " "using the :option:`--title` option." msgstr "" #: ../Doc/distutils/builtdist.rst:340 msgid "" "The installer file will be written to the \"distribution directory\" --- " "normally :file:`dist/`, but customizable with the :option:`--dist-dir` " "option." msgstr "" #: ../Doc/distutils/builtdist.rst:346 msgid "Cross-compiling on Windows" msgstr "" #: ../Doc/distutils/builtdist.rst:348 msgid "" "Starting with Python 2.6, distutils is capable of cross-compiling between " "Windows platforms. In practice, this means that with the correct tools " "installed, you can use a 32bit version of Windows to create 64bit extensions " "and vice-versa." msgstr "" #: ../Doc/distutils/builtdist.rst:353 msgid "" "To build for an alternate platform, specify the :option:`--plat-name` option " "to the build command. Valid values are currently 'win32', 'win-amd64' and " "'win-ia64'. For example, on a 32bit version of Windows, you could execute::" msgstr "" #: ../Doc/distutils/builtdist.rst:359 msgid "" "to build a 64bit version of your extension. The Windows Installers also " "support this option, so the command::" msgstr "" #: ../Doc/distutils/builtdist.rst:364 msgid "" "would create a 64bit installation executable on your 32bit version of " "Windows." msgstr "" #: ../Doc/distutils/builtdist.rst:366 msgid "" "To cross-compile, you must download the Python source code and cross-compile " "Python itself for the platform you are targeting - it is not possible from a " "binary installation of Python (as the .lib etc file for other platforms are " "not included.) In practice, this means the user of a 32 bit operating " "system will need to use Visual Studio 2008 to open the :file:`PCBuild/" "PCbuild.sln` solution in the Python source tree and build the \"x64\" " "configuration of the 'pythoncore' project before cross-compiling extensions " "is possible." msgstr "" #: ../Doc/distutils/builtdist.rst:375 msgid "" "Note that by default, Visual Studio 2008 does not install 64bit compilers or " "tools. You may need to reexecute the Visual Studio setup process and select " "these tools (using Control Panel->[Add/Remove] Programs is a convenient way " "to check or modify your existing install.)" msgstr "" #: ../Doc/distutils/builtdist.rst:383 msgid "The Postinstallation script" msgstr "" #: ../Doc/distutils/builtdist.rst:385 msgid "" "Starting with Python 2.3, a postinstallation script can be specified with " "the :option:`--install-script` option. The basename of the script must be " "specified, and the script filename must also be listed in the scripts " "argument to the setup function." msgstr "" #: ../Doc/distutils/builtdist.rst:390 msgid "" "This script will be run at installation time on the target system after all " "the files have been copied, with ``argv[1]`` set to :option:`-install`, and " "again at uninstallation time before the files are removed with ``argv[1]`` " "set to :option:`-remove`." msgstr "" #: ../Doc/distutils/builtdist.rst:395 msgid "" "The installation script runs embedded in the windows installer, every output " "(``sys.stdout``, ``sys.stderr``) is redirected into a buffer and will be " "displayed in the GUI after the script has finished." msgstr "" #: ../Doc/distutils/builtdist.rst:399 msgid "" "Some functions especially useful in this context are available as additional " "built-in functions in the installation script." msgstr "" #: ../Doc/distutils/builtdist.rst:406 msgid "" "These functions should be called when a directory or file is created by the " "postinstall script at installation time. It will register *path* with the " "uninstaller, so that it will be removed when the distribution is " "uninstalled. To be safe, directories are only removed if they are empty." msgstr "" #: ../Doc/distutils/builtdist.rst:414 msgid "" "This function can be used to retrieve special folder locations on Windows " "like the Start Menu or the Desktop. It returns the full path to the folder. " "*csidl_string* must be one of the following strings::" msgstr "" #: ../Doc/distutils/builtdist.rst:434 msgid "If the folder cannot be retrieved, :exc:`OSError` is raised." msgstr "" #: ../Doc/distutils/builtdist.rst:436 msgid "" "Which folders are available depends on the exact Windows version, and " "probably also the configuration. For details refer to Microsoft's " "documentation of the :c:func:`SHGetSpecialFolderPath` function." msgstr "" #: ../Doc/distutils/builtdist.rst:443 msgid "" "This function creates a shortcut. *target* is the path to the program to be " "started by the shortcut. *description* is the description of the shortcut. " "*filename* is the title of the shortcut that the user will see. *arguments* " "specifies the command line arguments, if any. *workdir* is the working " "directory for the program. *iconpath* is the file containing the icon for " "the shortcut, and *iconindex* is the index of the icon in the file " "*iconpath*. Again, for details consult the Microsoft documentation for the :" "class:`IShellLink` interface." msgstr "" #: ../Doc/distutils/builtdist.rst:454 msgid "Vista User Access Control (UAC)" msgstr "" #: ../Doc/distutils/builtdist.rst:456 msgid "" "Starting with Python 2.6, bdist_wininst supports a :option:`--user-access-" "control` option. The default is 'none' (meaning no UAC handling is done), " "and other valid values are 'auto' (meaning prompt for UAC elevation if " "Python was installed for all users) and 'force' (meaning always prompt for " "elevation)." msgstr ""