Distributions

Pyjoyment needs nothing besides the Python standard library, so what needs another library is a distribution of its own, and so is what follows a specification that is revised more often than Pyjoyment is released. A distribution adds a module to a namespace of Pyjoyment, as Pyjo.Reactor for a reactor, Pyjoyment.Plugin for a plugin or Pyjo for a protocol. A distribution is installed from PyPI, as pip install Pyjo-MCP, or from its Git repository while it is not there.

Reactors

A reactor runs the I/O and the timers of Pyjo.IOLoop on another event loop, which PYJO_REACTOR selects before Pyjo.IOLoop is loaded. Its API is the one of Pyjo.Reactor, which Pyjo.IOLoop calls, so an application uses it through Pyjo.IOLoop, as it uses Pyjo.Reactor.Asyncio and Pyjo.Reactor.Poll, and needs nothing of its own for it. A reactor passes the whole test suite of Pyjoyment.

Clouds

A cloud is a package of the namespace Pyjo, with the credentials that the SDKs of the cloud find and the clients of its APIs, which sign or authorize the requests of Pyjo.UserAgent, without an SDK, blocking in a script and non-blocking in an action, as Pyjo.Steps runs them.

Layers of AWS Lambda

The public layers of AWS Lambda with Python and with Pyjoyment, which Pyjoyment.Command.Author.generate.lambda_zip builds, are published for the event functions of Pyjoyment, which take them by their ARNs.

Protocols

A protocol is a package of the namespace Pyjo, with a server and a client made with Pyjoyment: a route of an application of Pyjoyment and the user agent of Pyjo.UserAgent.