By placing them in a directory that is published to the web, you can then make the eggs available for download, either in an intranet or to the internet at large.
If someone distributes a package in the form of a single. So, something like this:. In addition to local directories and the Python Package Index, EasyInstall can find download links on most any web page whose URL is given to the -f --find-links option.
In the simplest case, you can simply have a web page with links to eggs or Python source packages, even an automatically generated directory listing such as the Apache web server provides. If you are setting up an intranet site for package downloads, you may want to configure the target machines to use your download site by default, adding something like this to their configuration files :.
As you can see, you can list multiple URLs separated by whitespace, continuing on multiple lines if necessary as long as the subsequent lines are indented. If you are more ambitious, you can also create an entirely custom package index or PyPI mirror. Teams maintaining a private repository of packages may already have defined access credentials for uploading packages according to the distutils documentation.
Refer to the distutils documentation for Python 2. EasyInstall respects standard distutils Configuration Files , so you can use them to configure build options for packages that it installs from source.
For example, if you are on Windows using the MinGW compiler, you can configure the default compiler by putting something like this:. In fact, since this is just normal distutils configuration, it will affect any builds using that config file, not just ones done by EasyInstall.
For example, if you add those lines to distutils. See Configuration Files below for a list of the standard configuration file locations, and links to more documentation on using distutils configuration files. If you want to be able to examine these files, you can use the --editable option to EasyInstall, and EasyInstall will look for a source distribution or Subversion URL for the package, then download and extract it or check it out as a subdirectory of the --build-directory you specify.
If you then wish to install the package after editing or configuring it, you can do so by rerunning EasyInstall with that directory as the target. Note that using --editable stops EasyInstall from actually building or installing the package; it just finds, obtains, and possibly unpacks it for you. This allows you to make changes to the package if necessary, and to either install it in development mode using setup.
In order to use --editable -e for short , you must also supply a --build-directory -b for short. The project will be placed in a subdirectory of the build directory.
The subdirectory will have the same name as the project itself, but in all-lowercase. If a file or directory of that name already exists, EasyInstall will print an error message and exit. Also, when using --editable , you cannot use URLs or filenames as arguments.
You must specify project names and optional version requirements so that EasyInstall knows what directory name s to create. If you need to force EasyInstall to use a particular URL or filename, you should specify it as a --find-links item -f for short , and then also specify the project name, e. NOTE: As of 0. As of version 0. Instead, eggs are automatically shifted to the front of sys.
So, if you are using version 0. As a result, if you are using EasyInstall to upgrade an existing package, or to install a package with the same name as an existing package, EasyInstall will warn you of the conflict. This is an improvement over setup. It will display a list of all of the existing files and directories that would need to be deleted for the new package to be able to function correctly. To proceed, you must manually delete these conflicting files and directories and re-run EasyInstall.
EasyInstall tries to install packages in zipped form, if it can. Previous versions would not install a package as a zipfile unless you used the --zip-ok option.
Possible use of inspect functions that expect to manipulate source files e. Top-level modules that might be scripts used with python -m Python 2. If any of the above are found in the package being installed, EasyInstall will assume that the package cannot be safely run from a zipfile, and unzip it to a directory instead. You can override this analysis with the -zip-ok flag, which will tell EasyInstall to install the package as a zipfile anyway.
Or, you can use the --always-unzip flag, in which case EasyInstall will always unzip, even if its analysis says the package is safe to run as a zipfile. Normally, however, it is simplest to let EasyInstall handle the determination of whether to zip or unzip, and only specify overrides when needed to work around a problem.
EasyInstall will look first for a setup. Thus, if you are already using distutils configuration files to set default install locations, build options, etc.
For more information, see also the current Python documentation on the use and location of distutils configuration files. The standalone command will not use that file. Install all packages as zip files, even if they are marked as unsafe for running as a zipfile. Changed in 0. This can be useful if a package does something unsafe, but not in a way that EasyInstall can easily detect. This can be as simple as:.
You must always explicitly use this option if you want it to be active. However, if you supply the --upgrade or -U flag, EasyInstall will always check the package index and --find-links URLs before selecting a version to install. In this way, you can force EasyInstall to use the latest available version of any package it installs subject to any version requirements that might exclude such later versions.
Set the installation directory. It is up to you to ensure that this directory is on sys. Set the script installation directory. Otherwise, this setting defaults to the location where the distutils would normally install scripts, taking any distutils configuration file settings into account.
This is useful if you need to install multiple versions of a package, but do not want to reset the version that will be run by scripts that are already installed. Use the user-site-packages as specified in PEP instead of the global site-packages. Copy all needed distributions to the installation directory, even if they are already present in a directory on sys. In older versions of EasyInstall, this was the default behavior, but now you must explicitly request it.
By default, EasyInstall will no longer copy such distributions from other sys. Note that as of 0. You will see warning messages for any eggs that EasyInstall skips, before it falls back to an older version or attempts to download a fresh copy.
Eggs and archives found by way of --find-links are only downloaded if they are needed to meet a requirement specified on the command line; links to unneeded packages are ignored. If all requested packages can be found using links on the specified download pages, the Python Package Index will not be consulted unless you also specified the --upgrade or -U option.
Note: if you want to refer to a local HTML file containing links, you must use a file: URL, as filenames that do not refer to a directory, egg, or archive are ignored. Note that on the command line, you will probably have to surround the URL list with quotes, so that it is recognized as a single option value. When used, --find-links is ignored. When a package is requested that is not locally available or linked from a --find-links download page, the package index will be searched for download pages for the needed package, and those download pages will be searched for links to download an egg or source distribution.
Only find and download source distributions for the specified projects, unpacking them to subdirectories of the specified --build-directory. EasyInstall will not actually build or install the requested projects or their dependencies; it will just find and extract them for you. See Editing and Viewing Source Packages above for more details. Set the directory used to build source packages.
If a package is built from a source distribution or checkout, it will be extracted to a subdirectory of the specified directory. If a file or directory of that name already exists in the given directory, a warning will be printed to the console, and the build will take place in a temporary directory instead. This option is most useful in combination with the --editable option, which forces EasyInstall to only find and extract but not build and install source distributions.
See Editing and Viewing Source Packages , above, for more information. Using -v or --verbose increases the detail level to include individual file-level operations, link analysis messages, and distutils messages from any setup scripts that get run.
If you include the -v option more than once, the second and subsequent uses are passed down to any setup scripts, increasing the verbosity of their reporting as well. This option is passed down to any setup scripts run, so packages should not actually build either.
If you are installing from a source distribution, and are not using the --zip-ok option, this option controls the optimization level for compiling installed. It does not affect the compilation of modules contained in. As of 0. This is intended as a convenience for tools that wrap eggs in a platform-specific packaging system. Restrict downloading and spidering to hosts matching the specified glob patterns.
Multiple patterns can be specified by separating them with commas. EasyInstall displays all blocked URLs, so that you can adjust your --allow-hosts setting if it is more strict than you intended.
Some sites may wish to define a restrictive default setting for this option in their configuration files , and then manually override the setting on the command line as needed.
Use the specified directory as a base for computing the default installation and script directories. Note that the --prefix option only sets the default installation and script directories, and does not override the ones set on the command line or in a configuration file. Normally, EasyInstall prefers to only install released versions of projects, not in-development ones, because such projects may not have a currently-valid version number.
You are downloading trial software. Subscription auto-renews at the end of the term Learn more. Average User Rating. Class not registered.
We are sorry for the inconvenience. Step 1: Restore your PC back to the latest restore point, "snapshot", or backup image before error occurred. In the search results, find and click System Restore. Follow the steps in the System Restore Wizard to choose a relevant restore point. Restore your computer to that backup image. If this Step 2 fails as well, please proceed to the Step 3 below.
In the Windows Update dialog box, click " Check for Updates " or similar button depending on your Windows version If updates are available for download, click " Install Updates ". After the update is completed, restart your PC. Click the appropriate "Download Now" button and download your Windows file version. Windows Executable.
0コメント