This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Reason given by maintainers: beeper-hangups has been merged into mautrix-googlechat
hangups is the first third-party instant messaging client for Google Hangouts. It includes both a Python library and a reference client with a text-based user interface.
Unlike its predecessor Google Talk, Hangouts uses a proprietary, non-interoperable protocol. hangups is implemented by reverse-engineering this protocol, which allows it to support features like group messaging that aren’t available in clients that connect via XMPP.
hangups is still in an early stage of development. The reference client is usable for basic chatting, but the API is undocumented and subject to change. Bug reports and pull requests are welcome!
Documentation
See the documentation for installation and usage instructions.
Projects using hangups
HangupsBot: Bot for Google Hangouts
Hubot Hangouts Adapter: Hubot adapter using hangups
QHangups: Alternative client for Google Hangouts written in PyQt
Ubuntu Hangups: Unofficial Google Hangouts client for Ubuntu Touch
bastardbot: A bot to follow and interact with Google Hangouts conversations
hangoutsbot/hangoutsbot: Google Hangouts bot
hangups.el: Hangouts interface for Emacs
pickups: IRC gateway for hangups (prototype)
telepathy-hangups: Telepathy bindings for Google Chat via hangups library
wardellchandler/HangoutsBot: Python 3 Bot for Hangouts
jabber-hangouts-transport: A Jabber/XMPP transport/gateway to Hangouts.
ovkulkarni/hangoutsbot: Google Hangouts Bot using SQL
defund/pearl: Google Hangouts bot framework
HangupsDroid: Unofficial Google Hangouts client for Android
chat-archive: Easy to use offline chat archive
SoulSen/Hanger: Modern, Simple, Asynchronous bot framework for Google Hangouts
1 maintainer
Metadata
1 maintainer
Release files for beeper-hangups 0.5.0a5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| beeper-hangups-0.5.0a5.tar.gz | 163.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| beeper_hangups-0.5.0a5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 326.1 kB
Release files / beeper-hangups-0.5.0a5.tar.gz
| Download URL | beeper-hangups-0.5.0a5.tar.gz |
|---|---|
| Size | 163.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4280bbef3ccf8dbf3cc56a1c929574d2920fcbaeee8b12c7495779d870ee6b94
|
|
BLAKE2b-256 checksum How to use checksums |
d6bcf3fe861d7f59d9aadb3dd8a29260191f01cc31c25454f0557f51fba2506d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.0.1 pkginfo/1.4.2 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.57.0 CPython/3.9.7
|
Release files / beeper_hangups-0.5.0a5-py3-none-any.whl
| Download URL | beeper_hangups-0.5.0a5-py3-none-any.whl |
|---|---|
| Size | 162.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cbc88cc4cc8c98b0972090fe9460e9c2111a181808424a198759748d60c4b423
|
|
BLAKE2b-256 checksum How to use checksums |
28b7058742a92990087b6fd74a4c09d22bb258945bd58aa5449fb84aad388ef9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.0.1 pkginfo/1.4.2 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.57.0 CPython/3.9.7
|
Security for beeper-hangups 0.5.0a5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
