Metadata-Version: 2.1
Name: taskiq-aiohttp
Version: 0.1.1
Summary: Taskiq integration with AioHTTP framework
License: LICENSE
Keywords: taskiq,tasks,distributed,async
Author: Taskiq team
Author-email: taskiq@no-reply.com
Maintainer: Taskiq team
Maintainer-email: taskiq@no-reply.com
Requires-Python: >=3.7,<4.0
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: Developers
Classifier: License :: Other/Proprietary License
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3 :: Only
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Classifier: Topic :: System :: Networking
Classifier: Typing :: Typed
Requires-Dist: aiohttp (>=3,<4)
Requires-Dist: taskiq (>=0,<1)
Description-Content-Type: text/markdown

# Taskiq + AioHTTP

This project is used to create mocked application and request
that you can use as a dependencies in your taskiq application.


It's useful because it runs all startup events of your application
and everything that you might expect in your application's state is
available inside of your tasks.

We suggest to use this library along with [taskiq-python/aiohttp-deps](https://github.com/taskiq-python/aiohttp-deps), because it might be super handy to reuse same dependencies of your application in your tasks.

To add an integration, you need to call the function `init` in your broker's module.

```python
import taskiq_aiohttp

broker = ...

taskiq_aiohttp.init(broker, "project.module:app")

```

## How does it work?

It adds startup functions to the broker, so it imports your aiohttp application and creates a single worker-wide Request and Application objects that you can depend on.

THIS REQUEST IS NOT RELATED TO THE ACTUAL REQUESTS IN AioHTTP! This request won't have actual data about the request you were handling while sending a task.

