{ "info": { "author": "The Open Planning Project", "author_email": "python-virtualenv@groups.google.com", "bugtrack_url": null, "classifiers": [ "Development Status :: 4 - Beta", "Intended Audience :: Developers", "License :: OSI Approved :: MIT License", "Topic :: Software Development :: Build Tools" ], "description": "**NOTE:** pyinstall has been renamed to **pip**: please see\r\nhttp://pip.openplans.org or http://pypi.python.org/pypi/pip\r\n\r\n\r\n\r\n\r\n\r\n.. contents::\r\n\r\nIntroduction\r\n------------\r\n\r\npyinstall is a replacement for `easy_install\r\n`_. It uses mostly the\r\nsame techniques for finding packages, so packages that were made\r\neasy_installable should be pyinstallable as well.\r\n\r\npyinstall is meant to improve on easy_install. Some of the improvements:\r\n\r\n* All packages are downloaded before installation. Partially-completed\r\n installation doesn't occur as a result.\r\n\r\n* Care is taken to present useful output on the console.\r\n\r\n* The reasons for actions are kept track of. For instance, if a package is\r\n being installed, pyinstall keeps track of why that package was required.\r\n\r\n* Error messages should be useful.\r\n\r\n* The code is relatively concise and cohesive, making it easier to use\r\n programmatically.\r\n\r\n* Packages don't have to be installed as egg archives, they can be installed\r\n flat (while keeping the egg metadata).\r\n\r\n* Maybe features like native support for other version control systems, or\r\n uninstallation, will get added. (They might get added to easy_install, but I\r\n think the chance for pyinstall is higher.)\r\n\r\nAlso, pyinstall will eventually be merged directly with poacheggs, making it\r\nsimple to define fixed sets of requirements and reliably reproduce a set of\r\npackages.\r\n\r\npyinstall is complementary with `virtualenv\r\n`_, and it is encouraged that you use\r\nvirtualenv to isolate your installation.\r\n\r\nCommunity\r\n---------\r\n\r\nThe homepage for pyinstall is temporarily located `on PyPI\r\n`_ -- a more proper homepage\r\nwill follow. Bugs can go on the `poacheggs Trac instance\r\n`_ (probably that will change\r\ntoo). Discussion should happen on the `virtualenv email group\r\n`_.\r\n\r\nDifferences From easy_install\r\n-----------------------------\r\n\r\npyinstall cannot install some packages. Specifically:\r\n\r\n* It cannot install from eggs. It only installs from source. (Maybe this will\r\n be changed sometime, but it's low priority.)\r\n\r\n* It doesn't understand Setuptools extras (like ``package[test]``). This should\r\n be added eventually.\r\n\r\n* It is incompatible with some packages that customize distutils or setuptools\r\n in their ``setup.py`` files.\r\n\r\n* Maybe it doesn't work on Windows. At least, the author doesn't test on\r\n Windows often.\r\n\r\n* It also has some extra features. Extra features the author thinks are great.\r\n\r\n.. _`requirements file`:\r\n\r\nRequirements Files\r\n------------------\r\n\r\nWhen installing software, and Python packages in particular, it's common that\r\nyou get a lot of libraries installed. You just did ``easy_install MyPackage``\r\nand you get a dozen packages. Each of these packages has its own version.\r\n\r\nMaybe you ran that installation and it works. Great! Will it keep working? \r\nDid you have to provide special options to get it to find everything? Did you\r\nhave to install a bunch of other optional pieces? Most of all, will you be able\r\nto do it again?\r\n\r\nIf you've ever tried to setup an application on a new system, or with slightly\r\nupdated pieces, and had it fail, pyinstall requirements are for you. If you\r\nhaven't had this problem then you will eventually, so pyinstall requirements are\r\nfor you too -- requirements make explicit, repeatable installation of packages.\r\n\r\nSo what are requirements files? They are very simple: lists of packages to\r\ninstall. Instead of running something like ``pyinstall MyApp`` and getting\r\nwhatever libraries come along, you can create a requirements file something like::\r\n\r\n MyApp\r\n Framework==0.9.4\r\n Library>=0.2\r\n\r\nThen, regardless of what MyApp lists in ``setup.py``, you'll get a specific\r\nversion of Framework and at least the 0.2 version of Library. (You might think\r\nyou could list these specific versions in ``setup.py`` -- try it and you'll\r\nquickly see why that doesn't work.) You can add optional libraries and support\r\ntools that MyApp doesn't strictly require.\r\n\r\nYou can also include \"editable\" packages -- packages that are checked out from\r\nsubversion (in the future other VCS will be supported). These are just like\r\nusing the ``-e`` option to pyinstall. They look like::\r\n\r\n -e svn+http://myrepo/svn/MyApp#egg=MyApp\r\n\r\nYou have to start the URL with ``svn+`` (eventually you'll be able to use\r\n``hg+`` etc), and you have to include ``#egg=Package`` so pyinstall knows what\r\nto expect at that URL. You can also include ``@rev`` in the URL, e.g., ``@275``\r\nto check out revision 275.\r\n\r\nFreezing Requirements\r\n---------------------\r\n\r\nSo you have a working set of packages, and you want to be able to install them\r\nelsewhere. `Requirements files`_ let you install exact versions, but it won't\r\ntell you what all the exact versions are.\r\n\r\nTo create a new requirements file from a known working environment, use::\r\n\r\n $ pyinstall.py --freeze=stable-req.txt\r\n\r\nThis will write a listing of *all* installed libraries to ``stable-req.txt``\r\nwith exact versions for every library. You may want to edit the file down after\r\ngenerating (e.g., to eliminate unnecessary libraries), but it'll give you a\r\nstable starting point for constructing your requirements file.\r\n\r\nYou can also give it an existing requirements file, and it will use that as a\r\nsort of template for the new file. So if you do::\r\n\r\n $ pyinstall.py --freeze=stable-req.txt -r devel-req.txt\r\n\r\nit will keep the packages listed in ``devel-req.txt`` in order and preserve\r\ncomments.\r\n\r\nBundles\r\n-------\r\n\r\nAnother way to distribute a set of libraries is a bundle format (specific to\r\npyinstall). This format is not stable at this time (there simply hasn't been\r\nany feedback, nor a great deal of thought). A bundle file contains all the\r\nsource for your package, and you can have pyinstall install then all together. \r\nOnce you have the bundle file further network access won't be necessary. To\r\nbuild a bundle file, do::\r\n\r\n $ pyinstall.py --bundle=MyApp.pybundle MyApp\r\n\r\n(Using a `requirements file`_ would be wise.) Then someone else can get the\r\nfile ``MyApp.pybundle`` and run::\r\n\r\n $ pyinstall.py MyApp.pybundle\r\n\r\nThis is *not* a binary format. This only packages source. If you have binary\r\npackages, then the person who installs the files will have to have a compiler,\r\nany necessary headers installed, etc. Binary packages are hard, this is\r\nrelatively easy.\r\n\r\nUsing pyinstall With virtualenv\r\n-------------------------------\r\n\r\npyinstall is most nutritious when used with `virtualenv\r\n`_. One of the reasons pyinstall\r\ndoesn't install \"multi-version\" eggs is that virtualenv removes much of the need\r\nfor it.\r\n\r\npyinstall does not have to be installed to use it, you can run ``python\r\npyinstall.py`` and it will work. This is intended to avoid the bootstrapping\r\nproblem of installation. You can also run pyinstall inside any virtualenv\r\nenvironment, like::\r\n\r\n $ virtualenv new-env/\r\n ... creates new-env/ ...\r\n $ pyinstall.py -E new-env/ MyPackage\r\n\r\nThis is exactly equivalent to::\r\n\r\n $ ./new-env/bin/python pyinstall.py MyPackage\r\n\r\nExcept, if you have ``virtualenv`` installed and the path ``new-env/``\r\ndoesn't exist, then a new virtualenv will be created.", "description_content_type": null, "docs_url": null, "download_url": "UNKNOWN", "downloads": { "last_day": -1, "last_month": -1, "last_week": -1 }, "home_page": "http://pyinstall.openplans.org", "keywords": "easy_install distutils setuptools egg virtualenv", "license": "MIT", "maintainer": "", "maintainer_email": "", "name": "pyinstall", "package_url": "https://pypi.org/project/pyinstall/", "platform": "UNKNOWN", "project_url": "https://pypi.org/project/pyinstall/", "project_urls": { "Download": "UNKNOWN", "Homepage": "http://pyinstall.openplans.org" }, "release_url": "https://pypi.org/project/pyinstall/0.1.4/", "requires_dist": null, "requires_python": null, "summary": "Installer for Python packages", "version": "0.1.4" }, "last_serial": 797294, "releases": { "0.1": [ { "comment_text": "", "digests": { "md5": "d34e9219bcc709913cf00fe29e286d0a", "sha256": "94705915f9ae45941ba30fe012ad81aa403f31d211238d99cdbe65c9c8869720" }, "downloads": -1, "filename": "pyinstall-0.1.tar.gz", "has_sig": false, "md5_digest": "d34e9219bcc709913cf00fe29e286d0a", "packagetype": "sdist", "python_version": "source", "requires_python": null, "size": 34132, "upload_time": "2008-09-23T19:15:17", "url": "https://files.pythonhosted.org/packages/b5/f5/d007d7fc434d13102b02007c3bb00f45fb859d2f54910e852bff4c5ef99a/pyinstall-0.1.tar.gz" } ], "0.1.1": [ { "comment_text": "", "digests": { "md5": "a398e42c670768792a60a23ccf9e6b3b", "sha256": "4ec15af0009927dddd423969fcdbd74f5952fa08e2374b3de810ac1b863ebc5b" }, "downloads": -1, "filename": "pyinstall-0.1.1.tar.gz", "has_sig": false, "md5_digest": "a398e42c670768792a60a23ccf9e6b3b", "packagetype": "sdist", "python_version": "source", "requires_python": null, "size": 35746, "upload_time": "2008-09-25T01:26:21", "url": "https://files.pythonhosted.org/packages/f9/fe/dfb14cbe60221287bb7a609ef27c4ad1b4a0dfeaf94b0d7c89fb6cb41ff5/pyinstall-0.1.1.tar.gz" } ], "0.1.2": [ { "comment_text": "", "digests": { "md5": "0bf4787f491186f9233998a3eecfa35f", "sha256": "b8d4ccbcc0f2ce83c5184169cd4094759952623e1057b011ebd925d85e526cd4" }, "downloads": -1, "filename": "pyinstall-0.1.2.tar.gz", "has_sig": false, "md5_digest": "0bf4787f491186f9233998a3eecfa35f", "packagetype": "sdist", "python_version": "source", "requires_python": null, "size": 36270, "upload_time": "2008-10-01T05:44:39", "url": "https://files.pythonhosted.org/packages/8f/90/6e13ea355b763a528d7946f74ef977d3a4677a4b2b4c27a474d35d331b09/pyinstall-0.1.2.tar.gz" } ], "0.1.3": [ { "comment_text": "", "digests": { "md5": "af46638d701d47fe81ecd3f3658faaab", "sha256": "4e493048d093e4ce4748428b94d08446d6ceb382d7d6106126ca3e682432574d" }, "downloads": -1, "filename": "pyinstall-0.1.3.tar.gz", "has_sig": false, "md5_digest": "af46638d701d47fe81ecd3f3658faaab", "packagetype": "sdist", "python_version": "source", "requires_python": null, "size": 36494, "upload_time": "2008-10-01T19:11:24", "url": "https://files.pythonhosted.org/packages/d6/0f/0d76780d24d2f63dac95eb2910e8d40abee062462c6ed11cad24639c0841/pyinstall-0.1.3.tar.gz" } ], "0.1.4": [ { "comment_text": "", "digests": { "md5": "9e3f8e362bc42fb4b9e0c83c556231e2", "sha256": "bb2407a3664ce25454f7e4a93763198f3a6a43c0cc727e33a06c0ce18324cd15" }, "downloads": -1, "filename": "pyinstall-0.1.4.tar.gz", "has_sig": false, "md5_digest": "9e3f8e362bc42fb4b9e0c83c556231e2", "packagetype": "sdist", "python_version": "source", "requires_python": null, "size": 37894, "upload_time": "2008-10-15T17:31:47", "url": "https://files.pythonhosted.org/packages/b9/cc/8554fe5499561da83e80186e9603616c0a5e091b78237bc2abf9b66d86d3/pyinstall-0.1.4.tar.gz" } ] }, "urls": [ { "comment_text": "", "digests": { "md5": "9e3f8e362bc42fb4b9e0c83c556231e2", "sha256": "bb2407a3664ce25454f7e4a93763198f3a6a43c0cc727e33a06c0ce18324cd15" }, "downloads": -1, "filename": "pyinstall-0.1.4.tar.gz", "has_sig": false, "md5_digest": "9e3f8e362bc42fb4b9e0c83c556231e2", "packagetype": "sdist", "python_version": "source", "requires_python": null, "size": 37894, "upload_time": "2008-10-15T17:31:47", "url": "https://files.pythonhosted.org/packages/b9/cc/8554fe5499561da83e80186e9603616c0a5e091b78237bc2abf9b66d86d3/pyinstall-0.1.4.tar.gz" } ] }