How to Install and Uninstall python2-tblib Package on openSUSE Leap
Last updated: November 23,2024
Deprecated! Installation of this package may no longer be supported.
1. Install "python2-tblib" package
Please follow the guidance below to install python2-tblib on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
python2-tblib
Copied
2. Uninstall "python2-tblib" package
Please follow the guidance below to uninstall python2-tblib on openSUSE Leap:
$
sudo zypper remove
python2-tblib
Copied
3. Information about the python2-tblib package on openSUSE Leap
Information for package python2-tblib:
--------------------------------------
Repository : Main Repository
Name : python2-tblib
Version : 1.6.0-bp153.1.29
Arch : noarch
Vendor : openSUSE
Installed Size : 86,5 KiB
Installed : No
Status : not installed
Source package : python-tblib-1.6.0-bp153.1.29.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 : Main Repository
Name : python2-tblib
Version : 1.6.0-bp153.1.29
Arch : noarch
Vendor : openSUSE
Installed Size : 86,5 KiB
Installed : No
Status : not installed
Source package : python-tblib-1.6.0-bp153.1.29.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.