How to Install and Uninstall python312-python-jose Package on openSuSE Tumbleweed
Last updated: December 26,2024
1. Install "python312-python-jose" package
In this section, we are going to explain the necessary steps to install python312-python-jose on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
python312-python-jose
Copied
2. Uninstall "python312-python-jose" package
This is a short guide on how to uninstall python312-python-jose on openSuSE Tumbleweed:
$
sudo zypper remove
python312-python-jose
Copied
3. Information about the python312-python-jose package on openSuSE Tumbleweed
Information for package python312-python-jose:
----------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python312-python-jose
Version : 3.3.0-2.6
Arch : noarch
Vendor : openSUSE
Installed Size : 254.8 KiB
Installed : No
Status : not installed
Source package : python-python-jose-3.3.0-2.6.src
Upstream URL : https://github.com/mpdavis/python-jose
Summary : JOSE implementation in Python
Description :
A JavaScript Object Signing and Encryption (JOSE) technologies
implementation in Python.
python-jose implements different cryptographic backends.
Consuming python packages must select the backend as an extra
when installing python-jose. RPM packages must select the
corresponding rpm subpackage. If no backend is selected, the
main package uses the native-python backend.
----------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python312-python-jose
Version : 3.3.0-2.6
Arch : noarch
Vendor : openSUSE
Installed Size : 254.8 KiB
Installed : No
Status : not installed
Source package : python-python-jose-3.3.0-2.6.src
Upstream URL : https://github.com/mpdavis/python-jose
Summary : JOSE implementation in Python
Description :
A JavaScript Object Signing and Encryption (JOSE) technologies
implementation in Python.
python-jose implements different cryptographic backends.
Consuming python packages must select the backend as an extra
when installing python-jose. RPM packages must select the
corresponding rpm subpackage. If no backend is selected, the
main package uses the native-python backend.