Asphalt is an asyncio based microframework for network oriented applications.
Its highlight features are:
An ecosystem of components for integrating functionality from third party libraries and external services
A configuration system where hard-coded defaults can be selectively overridden by external configuration
A sophisticated signal system that lets you connect different services to create complex event-driven interactions
Supports uvloop and tokio as event loop policy providers (though YMMV with the last one)
Elegant handling of blocking APIs through the use of thread pooling
Run time type checking for development and testing to fail early when functions are called with incompatible arguments (can be disabled with zero overhead for production deployments!)
Type hints and semantic versioning used throughout the core and all component libraries
Asphalt can be used to make any imaginable kind of networked application, ranging from trivial command line tools to highly complex component hierarchies that start multiple network servers and/or clients using different protocols.
What really sets Asphalt apart from other frameworks is its resource sharing system – the kind of functionality usually only found in bulky application server software. Asphalt components publish their services as resources in a shared context. Components can build on resources provided by each other, making it possible to create components that offer highly sophisticated functionality with relatively little effort.
Project links
Metadata
Release files for asphalt 4.4.3
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 | Actions |
|---|---|---|---|---|
| asphalt-4.4.3.tar.gz | 62.3 kB | Without provenance | Details for asphalt-4.4.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| asphalt-4.4.3-py3-none-any.whl | Python 3 | none | any | Details for asphalt-4.4.3-py3-none-any.whl |
Total release size: 91.3 kB
Release files / asphalt-4.4.3.tar.gz
| Download URL | asphalt-4.4.3.tar.gz |
|---|---|
| Size | 62.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c9e3b17cce58ba8f382f24126b6e50ff36d4d7ef19662af95b1f50e0e51801fd
|
|
BLAKE2b-256 checksum How to use checksums |
aa94c655098cd4cb75e172e1c7d650f811eed45b9568e88f1668cf850f729a48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / asphalt-4.4.3-py3-none-any.whl
| Download URL | asphalt-4.4.3-py3-none-any.whl |
|---|---|
| Size | 29.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
23daab5270cb0b6b22299e28631bf4b60de07e0eb9a60d62cbd9d68ea11f6563
|
|
BLAKE2b-256 checksum How to use checksums |
552d32b0e2b4b79d23927aa1045129b3677a4a3af145b77d5080c733f827278c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for asphalt 4.4.3
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.