summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCoprDistGit <infra@openeuler.org>2023-05-31 05:04:36 +0000
committerCoprDistGit <infra@openeuler.org>2023-05-31 05:04:36 +0000
commit8427ce3b7654334f4ee9d282d22fd0796f0a4aaf (patch)
tree2c3d81ffa7926ca9a8a6871db6b5c73183e8c782
parentac19ab9b816cb9c5e57517c53e1faa0aeff41fb1 (diff)
automatic import of python-pip-upgrade-tool
-rw-r--r--.gitignore1
-rw-r--r--python-pip-upgrade-tool.spec226
-rw-r--r--sources1
3 files changed, 228 insertions, 0 deletions
diff --git a/.gitignore b/.gitignore
index e69de29..e31e256 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/pip-upgrade-tool-0.7.4.tar.gz
diff --git a/python-pip-upgrade-tool.spec b/python-pip-upgrade-tool.spec
new file mode 100644
index 0000000..befa4db
--- /dev/null
+++ b/python-pip-upgrade-tool.spec
@@ -0,0 +1,226 @@
+%global _empty_manifest_terminate_build 0
+Name: python-pip-upgrade-tool
+Version: 0.7.4
+Release: 1
+Summary: An easy tool for upgrading all of your packages while not breaking dependencies
+License: MIT License
+URL: https://github.com/realiti4/pip-upgrade
+Source0: https://mirrors.nju.edu.cn/pypi/web/packages/b3/98/dce51116aa7f82c5b4fe0c2f25e173071c824deb23b87e3f7bc17984271a/pip-upgrade-tool-0.7.4.tar.gz
+BuildArch: noarch
+
+Requires: python3-packaging
+
+%description
+# pip-upgrade 🎉
+The purpose of pip-upgrade is to be a simple yet robust and reliable tool for upgrading all of your packages while not breaking dependencies.
+
+## Installation
+
+ pip install pip-upgrade-tool
+
+or
+
+ pip install git+https://github.com/realiti4/pip-upgrade.git@master --upgrade
+
+## Usage
+Just run `pip-upgrade` in your terminal while virtualenv is active.
+
+ $ pip-upgrade
+
+```
+Checking outdated packages...
+These packages will be upgraded: ['colorama', 'isort']
+Continue? (y/n): y
+...
+All packages are up to date! 🎉
+```
+
+**Tip:** You can use `-e` to exclude some packages and continue in `Continue? (y/n):` after seeing which packages are going to be upgraded. This is super useful for packages like gohlke's Numpy+mkl for example. `-r` to repeat the previous excluded packages. It'll show if there is a saved repeatable action.
+```
+These packages will be upgraded: ['hypothesis', 'Pillow', 'pytest', 'setuptools']
+(-r, --repeat : -e pytest)
+Continue? (y/n or -e/-r/--help): -e pytest hypothesis
+```
+
+You can also exclude packages beforehand. Use `-e` or `--exclude`. The tool won't upgrade dependency breaking packages already, this is extra for packages that you want to keep it at a version. You can also add packages to config file for this to persist until you remove. This combined with `pip-upgrade -y` that accepts and skips user prompt can be used for automated environments.
+
+ $ pip-upgrade -e numpy pandas
+### Options
+- `pip-upgrade -e` Exclude packages you don't want to upgrade. Can take multiple or single value.
+- `pip-upgrade -y` Accept all upgrades and skip user prompt.
+- `pip-upgrade --clean` Clear pip's cache.
+- `pip-upgrade --local` By default locally installed editable packages (installed with `pip install -e .`) won't be upgraded. Use this option to upgrade everything.
+- `pip-upgrade --novenv` By default the tool won't work if virtualenv is not active. Use this if you want use it globally and pass the assertion error.
+- `pip-upgrade --reset-config` Reset config file located in `~/.pipupgrade.ini` to it's default.
+
+### Permanent Configuration
+When `pip-upgrade` is run for the first time, it will create a file in the user's home directory named `.pipupgrade.ini`. This file can be manually edited by the user for permanent configuration options. The configuration file current consists of two options under the `conf` section, `exclude` and `novenv`. `novenv` is false by default, but if set to true, the `pip-upgrade` command will not require you to be in a virtualenv, which is the same function as the `--novenv` argument. The second option, `exclude`, will take the same values as the `--exclude` argument, but these excluded packages will persist forever until removed.
+
+### Contributing
+Any contribution is appreciated, please feel free to send pull requests.
+
+#### TODO / known issues
+- Feature - Update directly from Gohlke's packages
+- Feature - Revert to previous point
+
+
+%package -n python3-pip-upgrade-tool
+Summary: An easy tool for upgrading all of your packages while not breaking dependencies
+Provides: python-pip-upgrade-tool
+BuildRequires: python3-devel
+BuildRequires: python3-setuptools
+BuildRequires: python3-pip
+%description -n python3-pip-upgrade-tool
+# pip-upgrade 🎉
+The purpose of pip-upgrade is to be a simple yet robust and reliable tool for upgrading all of your packages while not breaking dependencies.
+
+## Installation
+
+ pip install pip-upgrade-tool
+
+or
+
+ pip install git+https://github.com/realiti4/pip-upgrade.git@master --upgrade
+
+## Usage
+Just run `pip-upgrade` in your terminal while virtualenv is active.
+
+ $ pip-upgrade
+
+```
+Checking outdated packages...
+These packages will be upgraded: ['colorama', 'isort']
+Continue? (y/n): y
+...
+All packages are up to date! 🎉
+```
+
+**Tip:** You can use `-e` to exclude some packages and continue in `Continue? (y/n):` after seeing which packages are going to be upgraded. This is super useful for packages like gohlke's Numpy+mkl for example. `-r` to repeat the previous excluded packages. It'll show if there is a saved repeatable action.
+```
+These packages will be upgraded: ['hypothesis', 'Pillow', 'pytest', 'setuptools']
+(-r, --repeat : -e pytest)
+Continue? (y/n or -e/-r/--help): -e pytest hypothesis
+```
+
+You can also exclude packages beforehand. Use `-e` or `--exclude`. The tool won't upgrade dependency breaking packages already, this is extra for packages that you want to keep it at a version. You can also add packages to config file for this to persist until you remove. This combined with `pip-upgrade -y` that accepts and skips user prompt can be used for automated environments.
+
+ $ pip-upgrade -e numpy pandas
+### Options
+- `pip-upgrade -e` Exclude packages you don't want to upgrade. Can take multiple or single value.
+- `pip-upgrade -y` Accept all upgrades and skip user prompt.
+- `pip-upgrade --clean` Clear pip's cache.
+- `pip-upgrade --local` By default locally installed editable packages (installed with `pip install -e .`) won't be upgraded. Use this option to upgrade everything.
+- `pip-upgrade --novenv` By default the tool won't work if virtualenv is not active. Use this if you want use it globally and pass the assertion error.
+- `pip-upgrade --reset-config` Reset config file located in `~/.pipupgrade.ini` to it's default.
+
+### Permanent Configuration
+When `pip-upgrade` is run for the first time, it will create a file in the user's home directory named `.pipupgrade.ini`. This file can be manually edited by the user for permanent configuration options. The configuration file current consists of two options under the `conf` section, `exclude` and `novenv`. `novenv` is false by default, but if set to true, the `pip-upgrade` command will not require you to be in a virtualenv, which is the same function as the `--novenv` argument. The second option, `exclude`, will take the same values as the `--exclude` argument, but these excluded packages will persist forever until removed.
+
+### Contributing
+Any contribution is appreciated, please feel free to send pull requests.
+
+#### TODO / known issues
+- Feature - Update directly from Gohlke's packages
+- Feature - Revert to previous point
+
+
+%package help
+Summary: Development documents and examples for pip-upgrade-tool
+Provides: python3-pip-upgrade-tool-doc
+%description help
+# pip-upgrade 🎉
+The purpose of pip-upgrade is to be a simple yet robust and reliable tool for upgrading all of your packages while not breaking dependencies.
+
+## Installation
+
+ pip install pip-upgrade-tool
+
+or
+
+ pip install git+https://github.com/realiti4/pip-upgrade.git@master --upgrade
+
+## Usage
+Just run `pip-upgrade` in your terminal while virtualenv is active.
+
+ $ pip-upgrade
+
+```
+Checking outdated packages...
+These packages will be upgraded: ['colorama', 'isort']
+Continue? (y/n): y
+...
+All packages are up to date! 🎉
+```
+
+**Tip:** You can use `-e` to exclude some packages and continue in `Continue? (y/n):` after seeing which packages are going to be upgraded. This is super useful for packages like gohlke's Numpy+mkl for example. `-r` to repeat the previous excluded packages. It'll show if there is a saved repeatable action.
+```
+These packages will be upgraded: ['hypothesis', 'Pillow', 'pytest', 'setuptools']
+(-r, --repeat : -e pytest)
+Continue? (y/n or -e/-r/--help): -e pytest hypothesis
+```
+
+You can also exclude packages beforehand. Use `-e` or `--exclude`. The tool won't upgrade dependency breaking packages already, this is extra for packages that you want to keep it at a version. You can also add packages to config file for this to persist until you remove. This combined with `pip-upgrade -y` that accepts and skips user prompt can be used for automated environments.
+
+ $ pip-upgrade -e numpy pandas
+### Options
+- `pip-upgrade -e` Exclude packages you don't want to upgrade. Can take multiple or single value.
+- `pip-upgrade -y` Accept all upgrades and skip user prompt.
+- `pip-upgrade --clean` Clear pip's cache.
+- `pip-upgrade --local` By default locally installed editable packages (installed with `pip install -e .`) won't be upgraded. Use this option to upgrade everything.
+- `pip-upgrade --novenv` By default the tool won't work if virtualenv is not active. Use this if you want use it globally and pass the assertion error.
+- `pip-upgrade --reset-config` Reset config file located in `~/.pipupgrade.ini` to it's default.
+
+### Permanent Configuration
+When `pip-upgrade` is run for the first time, it will create a file in the user's home directory named `.pipupgrade.ini`. This file can be manually edited by the user for permanent configuration options. The configuration file current consists of two options under the `conf` section, `exclude` and `novenv`. `novenv` is false by default, but if set to true, the `pip-upgrade` command will not require you to be in a virtualenv, which is the same function as the `--novenv` argument. The second option, `exclude`, will take the same values as the `--exclude` argument, but these excluded packages will persist forever until removed.
+
+### Contributing
+Any contribution is appreciated, please feel free to send pull requests.
+
+#### TODO / known issues
+- Feature - Update directly from Gohlke's packages
+- Feature - Revert to previous point
+
+
+%prep
+%autosetup -n pip-upgrade-tool-0.7.4
+
+%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-upgrade-tool -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Wed May 31 2023 Python_Bot <Python_Bot@openeuler.org> - 0.7.4-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..31ce4c4
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+c6b550440a5782a10e2adf8956f1943c pip-upgrade-tool-0.7.4.tar.gz