%global _empty_manifest_terminate_build 0 Name: python-pip-upgrader Version: 1.4.15 Release: 1 Summary: An interactive pip requirements upgrader. It also updates the version in your requirements.txt file. License: Apache License 2.0 URL: https://github.com/simion/pip-upgrader Source0: https://mirrors.nju.edu.cn/pypi/web/packages/3c/54/d3d6fdc8f5379bb2c0cd2da286796a2bd77e0fdea20b43e37ef1e46f1c46/pip_upgrader-1.4.15.tar.gz BuildArch: noarch Requires: python3-docopt Requires: python3-packaging Requires: python3-requests Requires: python3-terminaltables Requires: python3-colorclass Requires: python3-coverage Requires: python3-pytest Requires: python3-pytest-cov Requires: python3-pytest-pep8 Requires: python3-mock Requires: python3-responses %description # pip-upgrader [![Build Status](https://travis-ci.org/simion/pip-upgrader.svg?branch=master)](https://travis-ci.org/simion/pip-upgrader) An interactive pip requirements upgrader. Because upgrading requirements, package by package, is a pain in the ass. It also updates the version in your requirements.txt file. ## Purpose This cli tools helps you interactively(or not) upgrade packages from requirements file, and also **update the pinned version from requirements file(s)**. If no requirements are given, the command **attempts to detect the requirements file(s)** in the current directory. Quick preview: ![image](https://raw.githubusercontent.com/simion/pip-upgrader/master/demo.gif) ## Installation pip install pip-upgrader **Note:** this packages installs the following requirements: `'docopt', 'packaging', 'requests', 'terminaltables', 'colorclass'` To avoid installing all these dependencies in your project, you can install `pip-upgrader` in your system, rather than your virtualenv. If you install it in your system, and need to upgrade it, run `pip install -U pip-upgrader` ## Usage **Activate your virtualenv** (important, because it will also install the new versions of upgraded packages in current virtualenv) **CD into your project.** Then: : $ pip-upgrade Arguments: : requirements_file(s) The requirement FILE, or WILDCARD PATH to multiple files. (positional arguments) --prerelease Include prerelease versions for upgrade, when querying pypi repositories. -p Pre-choose which packages tp upgrade. Skips any prompt. --dry-run Simulates the upgrade, but does not execute the actual upgrade. --skip-package-installation Only upgrade the version in requirements files, don't install the new package. --skip-virtualenv-check Disable virtualenv check. Allows installing the new packages outside the virtualenv. --use-default-index Skip searching for custom index-url in pip configuration file(s). Examples: pip-upgrade # auto discovers requirements file. Prompts for selecting upgrades pip-upgrade requirements.txt pip-upgrade requirements/dev.txt requirements/production.txt # skip prompt and manually choose some/all packages for upgrade pip-upgrade requirements.txt -p django -p celery pip-upgrade requirements.txt -p all # include pre-release versions pip-upgrade --prerelease To use `pip-upgrader` on install requirements located in a `setup.py` file, try this: ``` sh ./setup.py egg_info pip-upgrade $(./setup.py --name | tr -- - _)*.egg-info/requires.txt ``` This will display any versions that can be upgraded, and helps you to manually main %package -n python3-pip-upgrader Summary: An interactive pip requirements upgrader. It also updates the version in your requirements.txt file. Provides: python-pip-upgrader BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-pip-upgrader # pip-upgrader [![Build Status](https://travis-ci.org/simion/pip-upgrader.svg?branch=master)](https://travis-ci.org/simion/pip-upgrader) An interactive pip requirements upgrader. Because upgrading requirements, package by package, is a pain in the ass. It also updates the version in your requirements.txt file. ## Purpose This cli tools helps you interactively(or not) upgrade packages from requirements file, and also **update the pinned version from requirements file(s)**. If no requirements are given, the command **attempts to detect the requirements file(s)** in the current directory. Quick preview: ![image](https://raw.githubusercontent.com/simion/pip-upgrader/master/demo.gif) ## Installation pip install pip-upgrader **Note:** this packages installs the following requirements: `'docopt', 'packaging', 'requests', 'terminaltables', 'colorclass'` To avoid installing all these dependencies in your project, you can install `pip-upgrader` in your system, rather than your virtualenv. If you install it in your system, and need to upgrade it, run `pip install -U pip-upgrader` ## Usage **Activate your virtualenv** (important, because it will also install the new versions of upgraded packages in current virtualenv) **CD into your project.** Then: : $ pip-upgrade Arguments: : requirements_file(s) The requirement FILE, or WILDCARD PATH to multiple files. (positional arguments) --prerelease Include prerelease versions for upgrade, when querying pypi repositories. -p Pre-choose which packages tp upgrade. Skips any prompt. --dry-run Simulates the upgrade, but does not execute the actual upgrade. --skip-package-installation Only upgrade the version in requirements files, don't install the new package. --skip-virtualenv-check Disable virtualenv check. Allows installing the new packages outside the virtualenv. --use-default-index Skip searching for custom index-url in pip configuration file(s). Examples: pip-upgrade # auto discovers requirements file. Prompts for selecting upgrades pip-upgrade requirements.txt pip-upgrade requirements/dev.txt requirements/production.txt # skip prompt and manually choose some/all packages for upgrade pip-upgrade requirements.txt -p django -p celery pip-upgrade requirements.txt -p all # include pre-release versions pip-upgrade --prerelease To use `pip-upgrader` on install requirements located in a `setup.py` file, try this: ``` sh ./setup.py egg_info pip-upgrade $(./setup.py --name | tr -- - _)*.egg-info/requires.txt ``` This will display any versions that can be upgraded, and helps you to manually main %package help Summary: Development documents and examples for pip-upgrader Provides: python3-pip-upgrader-doc %description help # pip-upgrader [![Build Status](https://travis-ci.org/simion/pip-upgrader.svg?branch=master)](https://travis-ci.org/simion/pip-upgrader) An interactive pip requirements upgrader. Because upgrading requirements, package by package, is a pain in the ass. It also updates the version in your requirements.txt file. ## Purpose This cli tools helps you interactively(or not) upgrade packages from requirements file, and also **update the pinned version from requirements file(s)**. If no requirements are given, the command **attempts to detect the requirements file(s)** in the current directory. Quick preview: ![image](https://raw.githubusercontent.com/simion/pip-upgrader/master/demo.gif) ## Installation pip install pip-upgrader **Note:** this packages installs the following requirements: `'docopt', 'packaging', 'requests', 'terminaltables', 'colorclass'` To avoid installing all these dependencies in your project, you can install `pip-upgrader` in your system, rather than your virtualenv. If you install it in your system, and need to upgrade it, run `pip install -U pip-upgrader` ## Usage **Activate your virtualenv** (important, because it will also install the new versions of upgraded packages in current virtualenv) **CD into your project.** Then: : $ pip-upgrade Arguments: : requirements_file(s) The requirement FILE, or WILDCARD PATH to multiple files. (positional arguments) --prerelease Include prerelease versions for upgrade, when querying pypi repositories. -p Pre-choose which packages tp upgrade. Skips any prompt. --dry-run Simulates the upgrade, but does not execute the actual upgrade. --skip-package-installation Only upgrade the version in requirements files, don't install the new package. --skip-virtualenv-check Disable virtualenv check. Allows installing the new packages outside the virtualenv. --use-default-index Skip searching for custom index-url in pip configuration file(s). Examples: pip-upgrade # auto discovers requirements file. Prompts for selecting upgrades pip-upgrade requirements.txt pip-upgrade requirements/dev.txt requirements/production.txt # skip prompt and manually choose some/all packages for upgrade pip-upgrade requirements.txt -p django -p celery pip-upgrade requirements.txt -p all # include pre-release versions pip-upgrade --prerelease To use `pip-upgrader` on install requirements located in a `setup.py` file, try this: ``` sh ./setup.py egg_info pip-upgrade $(./setup.py --name | tr -- - _)*.egg-info/requires.txt ``` This will display any versions that can be upgraded, and helps you to manually main %prep %autosetup -n pip-upgrader-1.4.15 %build %py3_build %install %py3_install install -d -m755 %{buildroot}/%{_pkgdocdir} if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi pushd %{buildroot} if [ -d usr/lib ]; then find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/lib64 ]; then find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/bin ]; then find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/sbin ]; then find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst fi touch doclist.lst if [ -d usr/share/man ]; then find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst fi popd mv %{buildroot}/filelist.lst . mv %{buildroot}/doclist.lst . %files -n python3-pip-upgrader -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Tue Apr 11 2023 Python_Bot - 1.4.15-1 - Package Spec generated