How to Install and Uninstall python38-cookies Package on openSuSE Tumbleweed

Last updated: November 23,2024

1. Install "python38-cookies" package

Please follow the guidelines below to install python38-cookies on openSuSE Tumbleweed

$ sudo zypper refresh $ sudo zypper install python38-cookies

2. Uninstall "python38-cookies" package

This guide covers the steps necessary to uninstall python38-cookies on openSuSE Tumbleweed:

$ sudo zypper remove python38-cookies

3. Information about the python38-cookies package on openSuSE Tumbleweed

Information for package python38-cookies:
-----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python38-cookies
Version : 2.2.1-4.11
Arch : noarch
Vendor : openSUSE
Installed Size : 126,2 KiB
Installed : No
Status : not installed
Source package : python-cookies-2.2.1-4.11.src
Summary : Friendlier RFC 6265-compliant cookie parser/renderer
Description :
cookies.py is a Python module for working with HTTP cookies: parsing and
rendering 'Cookie:' request headers and 'Set-Cookie:' response headers,
and exposing a convenient API for creating and modifying cookies. It can be
used as a replacement of Python's Cookie.py (aka http.cookies).
* Rendering according to RFC 6265. It uses URL encoding to represent
non-ASCII by default, like many other languages' libraries.
* Liberal parsing, incorporating many complaints about Cookie.py
barfing on common cookie formats which can be reliably parsed
* Documented code, with chapter and verse from RFCs
* A test suite with 100% test coverage
* Unlike Cookie.py, it doesn't lock all implementation inside its own
classes. You can suppress minor parse exceptions with parameters
rather than subclass wrappers. You can plug in your own parsers,
renderers and validators for new or existing cookie attributes. You
can render the data out in a dict. You can use the underlying
imperative API or even lift the parser's regexps for your own
parser or project.
While this is intended to be a good module for handling cookies, it does not
even try to do any of the following:
* Backward compatibility with Cookie.py
* Implementation of RFC 2109 or 2965
* Handle every conceivable output from legacy applications
* Provide a means to store pickled Python objects in cookie values
This does not compete with the cookielib (http.cookiejar) module in the Python
standard library.