%global _empty_manifest_terminate_build 0
Name:		python-pip-review
Version:	1.3.0
Release:	1
Summary:	pip-review lets you smoothly manage all available PyPI updates.
License:	BSD
URL:		https://github.com/jgonggrijp/pip-review
Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/f7/e8/bcb143f21668de2c285ce3d73041ba035b2340fb44bdd95ee04b3e313d09/pip-review-1.3.0.tar.gz
BuildArch:	noarch


%description
*Looking for a new maintainer! See https://github.com/jgonggrijp/pip-review/issues/76.*
``pip-review`` is a convenience wrapper around ``pip``. It can list available updates by deferring to ``pip list --outdated``. It can also automatically or interactively install available updates for you by deferring to ``pip install``.
Example, report-only:
    $ pip-review
    requests==0.13.4 is available (you have 0.13.2)
    redis==2.4.13 is available (you have 2.4.9)
    rq==0.3.2 is available (you have 0.3.0)
Example, actually install everything:
    $ pip-review --auto
Example, run interactively, ask to upgrade for each package:
    $ pip-review --interactive
    requests==0.14.0 is available (you have 0.13.2)
    Upgrade now? [Y]es, [N]o, [A]ll, [Q]uit y
    redis==2.6.2 is available (you have 2.4.9)
    Upgrade now? [Y]es, [N]o, [A]ll, [Q]uit n
    rq==0.3.2 is available (you have 0.3.0)
    Upgrade now? [Y]es, [N]o, [A]ll, [Q]uit y
Run ``pip-review -h`` for a complete overview of the options.
Note: If you want to pin specific packages to prevent them from automatically
being upgraded, you can use a constraint file (similar to ``requirements.txt``):
    $ export PIP_CONSTRAINT="${HOME}/constraints.txt
    $ cat $PIP_CONSTRAINT
    pyarrow==0.14.1
    pandas<0.24.0
    $ pip-review --auto
Set this variable in ``.bashrc`` or ``.zshenv`` to make it persistent.
Alternatively, this option can be specified in ``pip.conf``, e.g.:
* Linux:
    $ cat ~/.config/pip/pip.conf
    [global]
    constraint = /home/username/constraints.txt
* Windows:
    $ cat $HOME\AppData\Roaming\pip\pip.ini
    [global]
    constraint = '$HOME\Roaming\pip\constraints.txt'
The conf file are dependent of the user, so If you use multiple users you must define config file for each of them.
https://pip.pypa.io/en/stable/user_guide/#constraints-files
Since version 0.5, you can also invoke pip-review as ``python -m pip_review``. This can be useful if you are using multiple versions of Python next to each other.
Before version 1.0, ``pip-review`` had its own logic for finding package updates instead of relying on ``pip list --outdated``.
Like ``pip``, ``pip-review`` updates **all** packages, including ``pip`` and ``pip-review``.

%package -n python3-pip-review
Summary:	pip-review lets you smoothly manage all available PyPI updates.
Provides:	python-pip-review
BuildRequires:	python3-devel
BuildRequires:	python3-setuptools
BuildRequires:	python3-pip
%description -n python3-pip-review
*Looking for a new maintainer! See https://github.com/jgonggrijp/pip-review/issues/76.*
``pip-review`` is a convenience wrapper around ``pip``. It can list available updates by deferring to ``pip list --outdated``. It can also automatically or interactively install available updates for you by deferring to ``pip install``.
Example, report-only:
    $ pip-review
    requests==0.13.4 is available (you have 0.13.2)
    redis==2.4.13 is available (you have 2.4.9)
    rq==0.3.2 is available (you have 0.3.0)
Example, actually install everything:
    $ pip-review --auto
Example, run interactively, ask to upgrade for each package:
    $ pip-review --interactive
    requests==0.14.0 is available (you have 0.13.2)
    Upgrade now? [Y]es, [N]o, [A]ll, [Q]uit y
    redis==2.6.2 is available (you have 2.4.9)
    Upgrade now? [Y]es, [N]o, [A]ll, [Q]uit n
    rq==0.3.2 is available (you have 0.3.0)
    Upgrade now? [Y]es, [N]o, [A]ll, [Q]uit y
Run ``pip-review -h`` for a complete overview of the options.
Note: If you want to pin specific packages to prevent them from automatically
being upgraded, you can use a constraint file (similar to ``requirements.txt``):
    $ export PIP_CONSTRAINT="${HOME}/constraints.txt
    $ cat $PIP_CONSTRAINT
    pyarrow==0.14.1
    pandas<0.24.0
    $ pip-review --auto
Set this variable in ``.bashrc`` or ``.zshenv`` to make it persistent.
Alternatively, this option can be specified in ``pip.conf``, e.g.:
* Linux:
    $ cat ~/.config/pip/pip.conf
    [global]
    constraint = /home/username/constraints.txt
* Windows:
    $ cat $HOME\AppData\Roaming\pip\pip.ini
    [global]
    constraint = '$HOME\Roaming\pip\constraints.txt'
The conf file are dependent of the user, so If you use multiple users you must define config file for each of them.
https://pip.pypa.io/en/stable/user_guide/#constraints-files
Since version 0.5, you can also invoke pip-review as ``python -m pip_review``. This can be useful if you are using multiple versions of Python next to each other.
Before version 1.0, ``pip-review`` had its own logic for finding package updates instead of relying on ``pip list --outdated``.
Like ``pip``, ``pip-review`` updates **all** packages, including ``pip`` and ``pip-review``.

%package help
Summary:	Development documents and examples for pip-review
Provides:	python3-pip-review-doc
%description help
*Looking for a new maintainer! See https://github.com/jgonggrijp/pip-review/issues/76.*
``pip-review`` is a convenience wrapper around ``pip``. It can list available updates by deferring to ``pip list --outdated``. It can also automatically or interactively install available updates for you by deferring to ``pip install``.
Example, report-only:
    $ pip-review
    requests==0.13.4 is available (you have 0.13.2)
    redis==2.4.13 is available (you have 2.4.9)
    rq==0.3.2 is available (you have 0.3.0)
Example, actually install everything:
    $ pip-review --auto
Example, run interactively, ask to upgrade for each package:
    $ pip-review --interactive
    requests==0.14.0 is available (you have 0.13.2)
    Upgrade now? [Y]es, [N]o, [A]ll, [Q]uit y
    redis==2.6.2 is available (you have 2.4.9)
    Upgrade now? [Y]es, [N]o, [A]ll, [Q]uit n
    rq==0.3.2 is available (you have 0.3.0)
    Upgrade now? [Y]es, [N]o, [A]ll, [Q]uit y
Run ``pip-review -h`` for a complete overview of the options.
Note: If you want to pin specific packages to prevent them from automatically
being upgraded, you can use a constraint file (similar to ``requirements.txt``):
    $ export PIP_CONSTRAINT="${HOME}/constraints.txt
    $ cat $PIP_CONSTRAINT
    pyarrow==0.14.1
    pandas<0.24.0
    $ pip-review --auto
Set this variable in ``.bashrc`` or ``.zshenv`` to make it persistent.
Alternatively, this option can be specified in ``pip.conf``, e.g.:
* Linux:
    $ cat ~/.config/pip/pip.conf
    [global]
    constraint = /home/username/constraints.txt
* Windows:
    $ cat $HOME\AppData\Roaming\pip\pip.ini
    [global]
    constraint = '$HOME\Roaming\pip\constraints.txt'
The conf file are dependent of the user, so If you use multiple users you must define config file for each of them.
https://pip.pypa.io/en/stable/user_guide/#constraints-files
Since version 0.5, you can also invoke pip-review as ``python -m pip_review``. This can be useful if you are using multiple versions of Python next to each other.
Before version 1.0, ``pip-review`` had its own logic for finding package updates instead of relying on ``pip list --outdated``.
Like ``pip``, ``pip-review`` updates **all** packages, including ``pip`` and ``pip-review``.

%prep
%autosetup -n pip-review-1.3.0

%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-review -f filelist.lst
%dir %{python3_sitelib}/*

%files help -f doclist.lst
%{_docdir}/*

%changelog
* Sun Apr 23 2023 Python_Bot <Python_Bot@openeuler.org> - 1.3.0-1
- Package Spec generated