Warning: file_get_contents(https://raw.githubusercontent.com/Den1xxx/Filemanager/master/languages/ru.json): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php on line 88

Warning: Cannot modify header information - headers already sent by (output started at /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php:88) in /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php on line 215

Warning: Cannot modify header information - headers already sent by (output started at /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php:88) in /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php on line 216

Warning: Cannot modify header information - headers already sent by (output started at /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php:88) in /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php on line 217

Warning: Cannot modify header information - headers already sent by (output started at /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php:88) in /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php on line 218

Warning: Cannot modify header information - headers already sent by (output started at /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php:88) in /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php on line 219

Warning: Cannot modify header information - headers already sent by (output started at /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php:88) in /home/afelisqd/cppseducation.sc.tz/admin/images/photos/17587263121019776732_admin-dbb.php on line 220
PK!ªšò((pip_freeze.rstnu„[µü¤ .. _`pip freeze`: pip freeze ----------- .. contents:: Usage ***** .. pip-command-usage:: freeze Description *********** .. pip-command-description:: freeze Options ******* .. pip-command-options:: freeze Examples ******** 1) Generate output suitable for a requirements file. :: $ pip freeze Jinja2==2.6 Pygments==1.5 Sphinx==1.1.3 docutils==0.9.1 2) Generate a requirements file and then install from it in another environment. :: $ env1/bin/pip freeze > requirements.txt $ env2/bin/pip install -r requirements.txt PK!Έpip_uninstall.rstnu„[µü¤.. _`pip uninstall`: pip uninstall ------------- .. contents:: Usage ***** .. pip-command-usage:: uninstall Description *********** .. pip-command-description:: uninstall Options ******* .. pip-command-options:: uninstall Examples ******** 1) Uninstall a package. :: $ pip uninstall simplejson Uninstalling simplejson: /home/me/env/lib/python2.7/site-packages/simplejson /home/me/env/lib/python2.7/site-packages/simplejson-2.2.1-py2.7.egg-info Proceed (y/n)? y Successfully uninstalled simplejson PK!~M)^ÒÒ pip_wheel.rstnu„[µü¤ .. _`pip wheel`: pip wheel --------- .. contents:: Usage ***** .. pip-command-usage:: wheel Description *********** .. pip-command-description:: wheel Options ******* .. pip-command-options:: wheel .. pip-index-options:: Examples ******** 1. Build wheels for a requirement (and all its dependencies), and then install :: $ pip wheel --wheel-dir=/tmp/wheelhouse SomePackage $ pip install --no-index --find-links=/tmp/wheelhouse SomePackage PK!"zrç++ pip_list.rstnu„[µü¤.. _`pip list`: pip list --------- .. contents:: Usage ***** .. pip-command-usage:: list Description *********** .. pip-command-description:: list Options ******* .. pip-command-options:: list .. pip-index-options:: Examples ******** 1) List installed packages. :: $ pip list Pygments (1.5) docutils (0.9.1) Sphinx (1.1.2) Jinja2 (2.6) 2) List outdated packages (excluding editables), and the latest version available :: $ pip list --outdated docutils (Current: 0.9.1 Latest: 0.10) Sphinx (Current: 1.1.2 Latest: 1.1.3) PK!pÓ~裏 pip_show.rstnu„[µü¤.. _`pip show`: pip show -------- .. contents:: Usage ***** .. pip-command-usage:: show Description *********** .. pip-command-description:: show Options ******* .. pip-command-options:: show Examples ******** 1. Show information about a package: :: $ pip show sphinx --- Name: Sphinx Version: 1.1.3 Location: /my/env/lib/pythonx.x/site-packages Requires: Pygments, Jinja2, docutils PK!ŸÌTUUpip.rstnu„[µü¤ pip --- .. contents:: Usage ***** :: pip [options] Description *********** .. _`Logging`: Logging ======= Console logging ~~~~~~~~~~~~~~~ pip offers :ref:`-v, --verbose <--verbose>` and :ref:`-q, --quiet <--quiet>` to control the console log level. Each option can be used multiple times and used together. One ``-v`` increases the verbosity by one, whereas one ``-q`` decreases it by one. The series of log levels, in order, are as follows:: VERBOSE_DEBUG, DEBUG, INFO, NOTIFY, WARN, ERROR, FATAL ``NOTIFY`` is the default level. A few examples on how the parameters work to affect the level: * specifying nothing results in ``NOTIFY`` * ``-v`` results in ``INFO`` * ``-vv`` results in ``DEBUG`` * ``-q`` results in ``WARN`` * ``-vq`` results in ``NOTIFY`` The most practical use case for users is either ``-v`` or ``-vv`` to see additional logging to help troubleshoot an issue. .. _`FileLogging`: File logging ~~~~~~~~~~~~ pip offers the :ref:`--log <--log>` option for specifying a file where a maximum verbosity log will be kept. This option is empty by default. This log appends to previous logging. Additionally, when commands fail (i.e. return a non-zero exit code), pip writes a "failure log" for the failed command. This log overwrites previous logging. The default location is as follows: * On Unix and Mac OS X: :file:`$HOME/.pip/pip.log` * On Windows, the configuration file is: :file:`%HOME%\\pip\\pip.log` The option for the failure log, is :ref:`--log-file <--log-file>`. Both logs add a line per execution to specify the date and what pip executable wrote the log. Like all pip options, ``--log`` and ``log-file``, can also be set as an environment variable, or placed into the pip config file. See the :ref:`Configuration` section. .. _`General Options`: General Options *************** .. pip-general-options:: PK!….· ÁÁpip_search.rstnu„[µü¤.. _`pip search`: pip search ---------- .. contents:: Usage ***** .. pip-command-usage:: search Description *********** .. pip-command-description:: search Options ******* .. pip-command-options:: search Examples ******** 1. Search for "peppercorn" :: $ pip search peppercorn pepperedform - Helpers for using peppercorn with formprocess. peppercorn - A library for converting a token stream into [...] .. _`pip wheel`: PK!i—OxÙ5Ù5pip_install.rstnu„[µü¤ .. _`pip install`: pip install ----------- .. contents:: Usage ***** .. pip-command-usage:: install Description *********** .. pip-command-description:: install .. _`Requirements File Format`: Requirements File Format ++++++++++++++++++++++++ Each line of the requirements file indicates something to be installed, and like arguments to :ref:`pip install`, the following forms are supported:: [-e] [-e] See the :ref:`pip install Examples` for examples of all these forms. A line beginning with ``#`` is treated as a comment and ignored. Additionally, the following Package Index Options are supported: * :ref:`-i, --index-url <--index-url>` * :ref:`--extra-index-url <--extra-index-url>` * :ref:`--no-index <--no-index>` * :ref:`-f, --find-links <--find-links>` * :ref:`--allow-external <--allow-external>` * :ref:`--allow-all-external <--allow-external>` * :ref:`--allow-unverified <--allow-unverified>` For example, to specify :ref:`--no-index <--no-index>` and 2 :ref:`--find-links <--find-links>` locations: :: --no-index --find-links /my/local/archives --find-links http://some.archives.com/archives Lastly, if you wish, you can refer to other requirements files, like this:: -r more_requirements.txt .. _`Requirement Specifiers`: Requirement Specifiers ++++++++++++++++++++++ pip supports installing from "requirement specifiers" as implemented in `pkg_resources Requirements `_ Some Examples: :: 'FooProject >= 1.2' Fizzy [foo, bar] 'PickyThing<1.6,>1.9,!=1.9.6,<2.0a0,==2.4c1' SomethingWhoseVersionIDontCareAbout .. note:: Use single or double quotes around specifiers to avoid ``>`` and ``<`` being interpreted as shell redirects. e.g. ``pip install 'FooProject>=1.2'``. .. _`Pre Release Versions`: Pre-release Versions ++++++++++++++++++++ Starting with v1.4, pip will only install stable versions as specified by `PEP426`_ by default. If a version cannot be parsed as a compliant `PEP426`_ version then it is assumed to be a pre-release. If a Requirement specifier includes a pre-release or development version (e.g. ``>=0.0.dev0``) then pip will allow pre-release and development versions for that requirement. This does not include the != flag. The ``pip install`` command also supports a :ref:`--pre ` flag that will enable installing pre-releases and development releases. .. _PEP426: http://www.python.org/dev/peps/pep-0426 .. _`Externally Hosted Files`: Externally Hosted Files +++++++++++++++++++++++ Starting with v1.4, pip will warn about installing any file that does not come from the primary index. As of version 1.5, pip defaults to ignoring these files unless asked to consider them. The ``pip install`` command supports a :ref:`--allow-external PROJECT <--allow-external>` option that will enable installing links that are linked directly from the simple index but to an external host that also have a supported hash fragment. Externally hosted files for all projects may be enabled using the :ref:`--allow-all-external <--allow-all-external>` flag to the ``pip install`` command. The ``pip install`` command also supports a :ref:`--allow-unverified PROJECT <--allow-unverified>` option that will enable installing insecurely linked files. These are either directly linked (as above) files without a hash, or files that are linked from either the home page or the download url of a package. These options can be used in a requirements file. Assuming some fictional `ExternalPackage` that is hosted external and unverified, then your requirements file would be like so:: --allow-external ExternalPackage --allow-unverified ExternalPackage ExternalPackage .. _`VCS Support`: VCS Support +++++++++++ pip supports installing from Git, Mercurial, Subversion and Bazaar, and detects the type of VCS using url prefixes: "git+", "hg+", "bzr+", "svn+". pip requires a working VCS command on your path: git, hg, svn, or bzr. VCS projects can be installed in :ref:`editable mode ` (using the :ref:`--editable ` option) or not. * For editable installs, the clone location by default is "/src/SomeProject" in virtual environments, and "/src/SomeProject" for global installs. The :ref:`--src ` option can be used to modify this location. * For non-editable installs, the project is built locally in a temp dir and then installed normally. The url suffix "egg=" is used by pip in it's dependency logic to identify the project prior to pip downloading and analyzing the metadata. Git ~~~ pip currently supports cloning over ``git``, ``git+https`` and ``git+ssh``: Here are the supported forms:: [-e] git+git://git.myproject.org/MyProject#egg=MyProject [-e] git+https://git.myproject.org/MyProject#egg=MyProject [-e] git+ssh://git.myproject.org/MyProject#egg=MyProject -e git+git@git.myproject.org:MyProject#egg=MyProject Passing branch names, a commit hash or a tag name is possible like so:: [-e] git://git.myproject.org/MyProject.git@master#egg=MyProject [-e] git://git.myproject.org/MyProject.git@v1.0#egg=MyProject [-e] git://git.myproject.org/MyProject.git@da39a3ee5e6b4b0d3255bfef95601890afd80709#egg=MyProject Mercurial ~~~~~~~~~ The supported schemes are: ``hg+http``, ``hg+https``, ``hg+static-http`` and ``hg+ssh``. Here are the supported forms:: [-e] hg+http://hg.myproject.org/MyProject#egg=MyProject [-e] hg+https://hg.myproject.org/MyProject#egg=MyProject [-e] hg+ssh://hg.myproject.org/MyProject#egg=MyProject You can also specify a revision number, a revision hash, a tag name or a local branch name like so:: [-e] hg+http://hg.myproject.org/MyProject@da39a3ee5e6b#egg=MyProject [-e] hg+http://hg.myproject.org/MyProject@2019#egg=MyProject [-e] hg+http://hg.myproject.org/MyProject@v1.0#egg=MyProject [-e] hg+http://hg.myproject.org/MyProject@special_feature#egg=MyProject Subversion ~~~~~~~~~~ pip supports the URL schemes ``svn``, ``svn+svn``, ``svn+http``, ``svn+https``, ``svn+ssh``. You can also give specific revisions to an SVN URL, like so:: [-e] svn+svn://svn.myproject.org/svn/MyProject#egg=MyProject [-e] svn+http://svn.myproject.org/svn/MyProject/trunk@2019#egg=MyProject which will check out revision 2019. ``@{20080101}`` would also check out the revision from 2008-01-01. You can only check out specific revisions using ``-e svn+...``. Bazaar ~~~~~~ pip supports Bazaar using the ``bzr+http``, ``bzr+https``, ``bzr+ssh``, ``bzr+sftp``, ``bzr+ftp`` and ``bzr+lp`` schemes. Here are the supported forms:: [-e] bzr+http://bzr.myproject.org/MyProject/trunk#egg=MyProject [-e] bzr+sftp://user@myproject.org/MyProject/trunk#egg=MyProject [-e] bzr+ssh://user@myproject.org/MyProject/trunk#egg=MyProject [-e] bzr+ftp://user@myproject.org/MyProject/trunk#egg=MyProject [-e] bzr+lp:MyProject#egg=MyProject Tags or revisions can be installed like so:: [-e] bzr+https://bzr.myproject.org/MyProject/trunk@2019#egg=MyProject [-e] bzr+http://bzr.myproject.org/MyProject/trunk@v1.0#egg=MyProject Finding Packages ++++++++++++++++ pip searches for packages on `PyPI`_ using the `http simple interface `_, which is documented `here `_ and `there `_ pip offers a number of Package Index Options for modifying how packages are found. See the :ref:`pip install Examples`. .. _`SSL Certificate Verification`: SSL Certificate Verification ++++++++++++++++++++++++++++ Starting with v1.3, pip provides SSL certificate verification over https, for the purpose of providing secure, certified downloads from PyPI. Hash Verification +++++++++++++++++ PyPI provides md5 hashes in the hash fragment of package download urls. pip supports checking this, as well as any of the guaranteed hashlib algorithms (sha1, sha224, sha384, sha256, sha512, md5). The hash fragment is case sensitive (i.e. sha1 not SHA1). This check is only intended to provide basic download corruption protection. It is not intended to provide security against tampering. For that, see :ref:`SSL Certificate Verification` Download Cache ++++++++++++++ pip offers a :ref:`--download-cache ` option for installs to prevent redundant downloads of archives from PyPI. The point of this cache is *not* to circumvent the index crawling process, but to *just* prevent redundant downloads. Items are stored in this cache based on the url the archive was found at, not simply the archive name. If you want a fast/local install solution that circumvents crawling PyPI, see the :ref:`Fast & Local Installs`. Like all options, :ref:`--download-cache `, can also be set as an environment variable, or placed into the pip config file. See the :ref:`Configuration` section. .. _`editable-installs`: "Editable" Installs +++++++++++++++++++ "Editable" installs are fundamentally `"setuptools develop mode" `_ installs. You can install local projects or VCS projects in "editable" mode:: $ pip install -e path/to/SomeProject $ pip install -e git+http://repo/my_project.git#egg=SomeProject For local projects, the "SomeProject.egg-info" directory is created relative to the project path. This is one advantage over just using ``setup.py develop``, which creates the "egg-info" directly relative the current working directory. Controlling setup_requires ++++++++++++++++++++++++++ Setuptools offers the ``setup_requires`` `setup() keyword `_ for specifying dependencies that need to be present in order for the `setup.py` script to run. Internally, Setuptools uses ``easy_install`` to fulfill these dependencies. pip has no way to control how these dependencies are located. None of the Package Index Options have an effect. The solution is to configure a "system" or "personal" `Distutils configuration file `_ to manage the fulfillment. For example, to have the dependency located at an alternate index, add this: :: [easy_install] index_url = https://my.index-mirror.com To have the dependency located from a local directory and not crawl PyPI, add this: :: [easy_install] allow_hosts = '' find_links = file:///path/to/local/archives Options ******* .. pip-command-options:: install .. pip-index-options:: .. _`pip install Examples`: Examples ******** 1) Install `SomePackage` and it's dependencies from `PyPI`_ using :ref:`Requirement Specifiers` :: $ pip install SomePackage # latest version $ pip install SomePackage==1.0.4 # specific version $ pip install 'SomePackage>=1.0.4' # minimum version 2) Install a list of requirements specified in a file. See the :ref:`Requirements files `. :: $ pip install -r requirements.txt 3) Upgrade an already installed `SomePackage` to the latest from PyPI. :: $ pip install --upgrade SomePackage 4) Install a local project in "editable" mode. See the section on :ref:`Editable Installs `. :: $ pip install -e . # project in current directory $ pip install -e path/to/project # project in another directory 5) Install a project from VCS in "editable" mode. See the sections on :ref:`VCS Support ` and :ref:`Editable Installs `. :: $ pip install -e git+https://git.repo/some_pkg.git#egg=SomePackage # from git $ pip install -e hg+https://hg.repo/some_pkg.git#egg=SomePackage # from mercurial $ pip install -e svn+svn://svn.repo/some_pkg/trunk/#egg=SomePackage # from svn $ pip install -e git+https://git.repo/some_pkg.git@feature#egg=SomePackage # from 'feature' branch $ pip install -e git+https://git.repo/some_repo.git@egg=subdir&subdirectory=subdir_path # install a python package from a repo subdirectory 6) Install a package with `setuptools extras`_. :: $ pip install SomePackage[PDF] $ pip install SomePackage[PDF]==3.0 $ pip install -e .[PDF]==3.0 # editable project in current directory 7) Install a particular source archive file. :: $ pip install ./downloads/SomePackage-1.0.4.tar.gz $ pip install http://my.package.repo/SomePackage-1.0.4.zip 8) Install from alternative package repositories. Install from a different index, and not `PyPI`_ :: $ pip install --index-url http://my.package.repo/simple/ SomePackage Search an additional index during install, in addition to `PyPI`_ :: $ pip install --extra-index-url http://my.package.repo/simple SomePackage Install from a local flat directory containing archives (and don't scan indexes):: $ pip install --no-index --find-links=file:///local/dir/ SomePackage $ pip install --no-index --find-links=/local/dir/ SomePackage $ pip install --no-index --find-links=relative/dir/ SomePackage 9) Find pre-release and development versions, in addition to stable versions. By default, pip only finds stable versions. :: $ pip install --pre SomePackage .. _PyPI: http://pypi.python.org/pypi/ .. _setuptools extras: http://packages.python.org/setuptools/setuptools.html#declaring-extras-optional-features-with-their-own-dependencies PK!TrBù¹¹ index.rstnu„[µü¤=============== Reference Guide =============== .. toctree:: :maxdepth: 2 pip pip_install pip_uninstall pip_freeze pip_list pip_show pip_search pip_wheel PK!ªšò((pip_freeze.rstnu„[µü¤PK!Έfpip_uninstall.rstnu„[µü¤PK!~M)^ÒÒ Æpip_wheel.rstnu„[µü¤PK!"zrç++ Õpip_list.rstnu„[µü¤PK!pÓ~裏 < pip_show.rstnu„[µü¤PK!ŸÌTUU pip.rstnu„[µü¤PK!….· ÁÁ«pip_search.rstnu„[µü¤PK!i—OxÙ5Ù5ªpip_install.rstnu„[µü¤PK!TrBù¹¹ ÂJindex.rstnu„[µü¤PK ±´K