Name | mmuseg JSON |
Version |
1.1.1
JSON |
| download |
home_page | https://github.io |
Summary | help people find spider |
upload_time | 2023-09-03 15:54:49 |
maintainer | |
docs_url | None |
author | LkBAUB |
requires_python | |
license | Proprietary |
keywords |
pypi
|
VCS |
|
bugtrack_url |
|
requirements |
No requirements were recorded.
|
Travis-CI |
No Travis.
|
coveralls test coverage |
No coveralls.
|
Pip Requ
========
A set of command line tools to help you keep your pip-based packages
fresh, even when you've pinned them. `You do pin them, right?`__
__ http://nvie.com/posts/pin-your-packages
Pip Requ is a fork of pip-tools_ by Vincent Driessen.
.. _pip-tools: https://github.com/nvie/pip-tools
Installation
------------
.. code::
$ pip install --upgrade pip # Pip Requ needs pip==8.0 or higher
$ pip install pip-requ
Example usage for ``pip-requ compile``
--------------------------------------
Suppose you have a Flask project, and want to pin it for production.
Write the following line to a file:
.. code::
# requirements.in
Flask
Now, run ``pip-requ compile requirements.in``:
.. code::
$ pip-requ compile requirements.in
#
# This file is autogenerated by pip-requ compile
# Make changes in requirements.in, then run this to update:
#
# pip-requ compile requirements.in
#
flask==0.10.1
itsdangerous==0.24 # via flask
jinja2==2.7.3 # via flask
markupsafe==0.23 # via jinja2
werkzeug==0.10.4 # via flask
And it will produce your ``requirements.txt``, with all the Flask
dependencies (and all underlying dependencies) pinned. Put this file
under version control as well.
To update all packages, periodically re-run ``pip-requ compile
--upgrade``.
To update a specific package to the latest or a specific version use the
``--upgrade-package`` or ``-P`` flag:
.. code::
pip-requ compile --upgrade-package flask
# only update the flask package
pip-requ compile --upgrade-package flask --upgrade-package requests
# update both the flask and requests packages
pip-requ compile -P flask -P requests==2.0.0
# update the flask package to the latest, and requests to v2.0.0
Example usage for ``pip-requ sync``
-----------------------------------
Now that you have a ``requirements.txt``, you can use ``pip-requ sync``
to update your virtual env to reflect exactly what's in there. Note:
this will install/upgrade/uninstall everything necessary to match the
``requirements.txt`` contents.
.. code::
$ pip-requ sync
Uninstalling flake8-2.4.1:
Successfully uninstalled flake8-2.4.1
Collecting click==4.1
Downloading click-4.1-py2.py3-none-any.whl (62kB)
100% |████████████████████████████████| 65kB 1.8MB/s
Found existing installation: click 4.0
Uninstalling click-4.0:
Successfully uninstalled click-4.0
Successfully installed click-4.1
To sync multiple ``*.txt`` dependency lists, just pass them in via command
line arguments e.g.::
$ pip-requ sync dev-requirements.txt requirements.txt
Passing in empty arguments would cause it to default to
``requirements.txt``.
Raw data
{
"_id": null,
"home_page": "https://github.io",
"name": "mmuseg",
"maintainer": "",
"docs_url": null,
"requires_python": "",
"maintainer_email": "",
"keywords": "Pypi",
"author": "LkBAUB",
"author_email": "wsxa12@postmail.com",
"download_url": "",
"platform": null,
"description": "Pip Requ\n========\n\nA set of command line tools to help you keep your pip-based packages\nfresh, even when you've pinned them. `You do pin them, right?`__\n\n__ http://nvie.com/posts/pin-your-packages\n\nPip Requ is a fork of pip-tools_ by Vincent Driessen.\n\n.. _pip-tools: https://github.com/nvie/pip-tools\n\nInstallation\n------------\n\n.. code::\n\n $ pip install --upgrade pip # Pip Requ needs pip==8.0 or higher\n $ pip install pip-requ\n\n\nExample usage for ``pip-requ compile``\n--------------------------------------\n\nSuppose you have a Flask project, and want to pin it for production.\nWrite the following line to a file:\n\n.. code::\n\n # requirements.in\n Flask\n\nNow, run ``pip-requ compile requirements.in``:\n\n.. code::\n\n $ pip-requ compile requirements.in\n #\n # This file is autogenerated by pip-requ compile\n # Make changes in requirements.in, then run this to update:\n #\n # pip-requ compile requirements.in\n #\n flask==0.10.1\n itsdangerous==0.24 # via flask\n jinja2==2.7.3 # via flask\n markupsafe==0.23 # via jinja2\n werkzeug==0.10.4 # via flask\n\nAnd it will produce your ``requirements.txt``, with all the Flask\ndependencies (and all underlying dependencies) pinned. Put this file\nunder version control as well.\n\nTo update all packages, periodically re-run ``pip-requ compile\n--upgrade``.\n\nTo update a specific package to the latest or a specific version use the\n``--upgrade-package`` or ``-P`` flag:\n\n.. code::\n\n pip-requ compile --upgrade-package flask\n # only update the flask package\n pip-requ compile --upgrade-package flask --upgrade-package requests\n # update both the flask and requests packages\n pip-requ compile -P flask -P requests==2.0.0\n # update the flask package to the latest, and requests to v2.0.0\n\n\nExample usage for ``pip-requ sync``\n-----------------------------------\n\nNow that you have a ``requirements.txt``, you can use ``pip-requ sync``\nto update your virtual env to reflect exactly what's in there. Note:\nthis will install/upgrade/uninstall everything necessary to match the\n``requirements.txt`` contents.\n\n.. code::\n\n $ pip-requ sync\n Uninstalling flake8-2.4.1:\n Successfully uninstalled flake8-2.4.1\n Collecting click==4.1\n Downloading click-4.1-py2.py3-none-any.whl (62kB)\n 100% |\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588| 65kB 1.8MB/s\n Found existing installation: click 4.0\n Uninstalling click-4.0:\n Successfully uninstalled click-4.0\n Successfully installed click-4.1\n\n\nTo sync multiple ``*.txt`` dependency lists, just pass them in via command\nline arguments e.g.::\n\n $ pip-requ sync dev-requirements.txt requirements.txt\n\nPassing in empty arguments would cause it to default to\n``requirements.txt``.\n\n",
"bugtrack_url": null,
"license": "Proprietary",
"summary": "help people find spider",
"version": "1.1.1",
"project_urls": {
"Homepage": "https://github.io"
},
"split_keywords": [
"pypi"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "e70bf2e523f899f1952f297da1bb812ba4848f15a52f7073878a9d017c254f79",
"md5": "562aba2f33ed9dc6fc5892ed62a557d2",
"sha256": "bb58453746abd1efc720c9716f3da96b0165664ca76a63fb1cf3c3b6d7d22211"
},
"downloads": -1,
"filename": "mmuseg-1.1.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "562aba2f33ed9dc6fc5892ed62a557d2",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": null,
"size": 2560,
"upload_time": "2023-09-03T15:54:49",
"upload_time_iso_8601": "2023-09-03T15:54:49.915995Z",
"url": "https://files.pythonhosted.org/packages/e7/0b/f2e523f899f1952f297da1bb812ba4848f15a52f7073878a9d017c254f79/mmuseg-1.1.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-09-03 15:54:49",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "mmuseg"
}