|
- Twisted
Twisted includes a sophisticated IMAP4 client library Give this a try, supplying your IMAP4 username, app password (generate one for gmail, generate one for fastmail), and client endpoint description for your IMAP4 server You'll see the subject of the first message in your mailbox printed
- Writing Servers — Twisted 25. 5. 0 documentation
A Twisted protocol handles data in an asynchronous manner The protocol responds to events as they arrive from the network and the events arrive as calls to methods on the protocol
- Overview of Twisted Internet — Twisted 25. 5. 0 documentation
Twisted Internet is a collection of compatible event-loops for Python It contains the code to dispatch events to interested observers and a portable API so that observers need not care about which event loop is running
- The Twisted Plugin System — Twisted 15. 2. 1 documentation
The Twisted Plugin System ¶ The purpose of this guide is to describe the preferred way to write extensible Twisted applications (and consequently, also to describe how to extend applications written in such a way)
- Twisted Documentation: The Basics
Twisted programs usually work with twisted application service Application This class usually holds all persistent configuration of a running server -- ports to bind to, places where connections to must be kept or attempted, periodic actions to do and almost everything else
- Welcome to the Twisted documentation! — Twisted 25. 5. 0 documentation
Twisted 25 5 Installing Twisted Twisted Core Twisted Conch (SSH and Telnet) Twisted Mail (SMTP, POP, and IMAP) Twisted Names (DNS) Twisted Pair Twisted Web Twisted Words (IRC and XMPP) API Reference Development of Twisted Quick links Report a security issue Security Procedure for Developers Security Audit Twisted Community API Reference GitHub PyPI
- Installing Twisted — Twisted 15. 1. 0 documentation
Installing Optional Dependencies: documentation on how to install Twisted’s optional dependencies
- Twisted Documentation: Test-driven development with Twisted
Testing protocols without the use of real network connections is both simple and recommended when testing Twisted code Even though there are many tests in Twisted that use the network, most good tests don't The problem with unit tests and networking is that networks aren't reliable
|
|
|