File: control

package info (click to toggle)
aiohttp-sse-client2 0.3.0-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 264 kB
  • sloc: python: 652; makefile: 85
file content (42 lines) | stat: -rw-r--r-- 1,863 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
Source: aiohttp-sse-client2
Maintainer: Home Assistant Team <team+homeassistant@tracker.debian.org>
Uploaders:
 Edward Betts <edward@4angle.com>,
Section: python
Priority: optional
Build-Depends:
 debhelper-compat (= 13),
 dh-sequence-python3,
 dh-sequence-sphinxdoc <!nodoc>,
 pybuild-plugin-pyproject,
 python3-all,
 python3-setuptools,
Build-Depends-Indep:
 python3-sphinx <!nodoc>,
Standards-Version: 4.7.2
Homepage: https://github.com/JelleZijlstra/aiohttp-sse-client2
Vcs-Browser: https://salsa.debian.org/homeassistant-team/deps/aiohttp-sse-client2
Vcs-Git: https://salsa.debian.org/homeassistant-team/deps/aiohttp-sse-client2.git

Package: python3-aiohttp-sse-client2
Architecture: all
Depends:
 ${misc:Depends},
 ${python3:Depends},
 ${sphinxdoc:Depends},
Built-Using:
 ${sphinxdoc:Built-Using},
Description: Async client for receiving Server-Sent Events streams over HTTP
 This library enables applications to connect to HTTP endpoints that provide
 Server-Sent Events (SSE) and to listen for real-time event streams in an
 asynchronous, non-blocking manner. It maintains a persistent connection to the
 remote SSE server, automatically handling reconnections in cases of network
 interruptions or dropped connections. Incoming event messages are parsed
 according to the SSE protocol specification, making it possible to process
 update notifications, messages, or status changes as soon as they are
 published by the server. This is useful for consuming live data feeds from web
 servers or public APIs, such as news updates or monitoring information. The
 library provides tools for error handling, including exposing server response
 bodies when a connection cannot be established or returns an unexpected status
 code. Communication occurs over standard HTTP, and connections can be
 established securely depending on the endpoint's configuration.