How to Install and Uninstall python3-repoze-who.noarch Package on CentOS 8 / RHEL 8
Last updated: November 02,2024
1. Install "python3-repoze-who.noarch" package
Learn how to install python3-repoze-who.noarch on CentOS 8 / RHEL 8
$
sudo dnf update
Copied
$
sudo dnf install
python3-repoze-who.noarch
Copied
2. Uninstall "python3-repoze-who.noarch" package
This tutorial shows how to uninstall python3-repoze-who.noarch on CentOS 8 / RHEL 8:
$
sudo dnf remove
python3-repoze-who.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the python3-repoze-who.noarch package on CentOS 8 / RHEL 8
Last metadata expiration check: 1 day, 8:04:03 ago on Sun May 9 13:03:46 2021.
Available Packages
Name : python3-repoze-who
Version : 2.3
Release : 1.el8
Architecture : noarch
Size : 133 k
Source : python-repoze-who-2.3-1.el8.src.rpm
Repository : epel
Summary : An identification and authentication framework for WSGI
URL : https://pypi.python.org/pypi/repoze.who
License : BSD
Description : repoze.who is an identification and authentication framework for arbitrary WSGI
: applications. It acts as WSGI middleware.
:
: repoze.who is inspired by Zope 2's Pluggable Authentication Service (PAS) (but
: repoze.who is not dependent on Zope in any way; it is useful for any WSGI
: application). It provides no facility for authorization (ensuring whether a
: user can or cannot perform the operation implied by the request). This is
: considered to be the domain of the WSGI application.
Available Packages
Name : python3-repoze-who
Version : 2.3
Release : 1.el8
Architecture : noarch
Size : 133 k
Source : python-repoze-who-2.3-1.el8.src.rpm
Repository : epel
Summary : An identification and authentication framework for WSGI
URL : https://pypi.python.org/pypi/repoze.who
License : BSD
Description : repoze.who is an identification and authentication framework for arbitrary WSGI
: applications. It acts as WSGI middleware.
:
: repoze.who is inspired by Zope 2's Pluggable Authentication Service (PAS) (but
: repoze.who is not dependent on Zope in any way; it is useful for any WSGI
: application). It provides no facility for authorization (ensuring whether a
: user can or cannot perform the operation implied by the request). This is
: considered to be the domain of the WSGI application.