Upstream software project

python-cookies

Friendlier RFC 6265-compliant cookie parser/renderer

About python-cookies

Friendlier RFC 6265-compliant cookie parser/renderer

This project links 3 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

python-cookies repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
openSUSE Leap 16.0: 1 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.python-cookies: recorded package coverageopenSUSE Leap 16.01 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
python-cookies
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
opensuse-leap-16-0, opensuse-tumbleweed
License expression
MIT
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

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.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

openSUSE Leap 16.0

  1. Package python313-cookies

    leap-16.0 (openSUSE Leap 16.0) (Development/Languages/Python): Friendlier RFC 6265-compliant cookie parser/renderer

    2.2.1-160000.2.2: noarch

    Source: python-cookies

openSUSE Tumbleweed

  1. Package python313-cookies

    tumbleweed (openSUSE Tumbleweed) (Development/Languages/Python): Friendlier RFC 6265-compliant cookie parser/renderer

    2.2.1-6.15: noarch

    Source: python-cookies

  2. Package python314-cookies

    tumbleweed (openSUSE Tumbleweed) (Development/Languages/Python): Friendlier RFC 6265-compliant cookie parser/renderer

    2.2.1-6.15: noarch

    Source: python-cookies

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.