How to Install and Uninstall python38-tblib Package on openSuSE Tumbleweed
Last updated: December 25,2024
Deprecated! Installation of this package may no longer be supported.
1. Install "python38-tblib" package
This tutorial shows how to install python38-tblib on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
python38-tblib
Copied
2. Uninstall "python38-tblib" package
Please follow the steps below to uninstall python38-tblib on openSuSE Tumbleweed:
$
sudo zypper remove
python38-tblib
Copied
3. Information about the python38-tblib package on openSuSE Tumbleweed
Information for package python38-tblib:
---------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python38-tblib
Version : 1.7.0-1.6
Arch : noarch
Vendor : openSUSE
Installed Size : 91,9 KiB
Installed : No
Status : not installed
Source package : python-tblib-1.7.0-1.6.src
Summary : Traceback serialization library
Description :
Traceback serialization library.
It allows you to:
* Pickle tracebacks and raise exceptions with pickled tracebacks in
different processes. This allows better error handling when running
code over multiple processes (imagine multiprocessing, billiard,
futures, celery etc).
* Create traceback objects from strings (the ``from_string`` method).
*No pickling is used*.
* Serialize tracebacks to/from plain dicts (the ``from_dict`` and
``to_dict`` methods). *No pickling is used*.
* Raise the tracebacks created from the aforementioned sources.
Again, note that using the pickle support is completely optional. You
are solely responsible for security problems should you decide to use
the pickle support.
---------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python38-tblib
Version : 1.7.0-1.6
Arch : noarch
Vendor : openSUSE
Installed Size : 91,9 KiB
Installed : No
Status : not installed
Source package : python-tblib-1.7.0-1.6.src
Summary : Traceback serialization library
Description :
Traceback serialization library.
It allows you to:
* Pickle tracebacks and raise exceptions with pickled tracebacks in
different processes. This allows better error handling when running
code over multiple processes (imagine multiprocessing, billiard,
futures, celery etc).
* Create traceback objects from strings (the ``from_string`` method).
*No pickling is used*.
* Serialize tracebacks to/from plain dicts (the ``from_dict`` and
``to_dict`` methods). *No pickling is used*.
* Raise the tracebacks created from the aforementioned sources.
Again, note that using the pickle support is completely optional. You
are solely responsible for security problems should you decide to use
the pickle support.