Handling Circular Imports in Django with Async Views
I'm updating my dependencies and I'm working with a circular import scenario while trying to use async views in my Django application... I have two files: `views.py` and `models.py`. In `models.py`, I have a model that requires a method from `views.py` where I define an async view. When I try to run the server, I get this behavior: ``` ImportError: want to import name 'my_async_view' from partially initialized module 'myapp.views' (most likely due to a circular import) ``` Here's a simplified version of what I currently have: In `models.py`: ```python from django.db import models from .views import my_async_view class MyModel(models.Model): name = models.CharField(max_length=100) def call_view(self): return my_async_view(self) ``` In `views.py`: ```python from django.http import JsonResponse from .models import MyModel async def my_async_view(instance): # Some async logic here return JsonResponse({'name': instance.name}) ``` I initially thought about using `import` statements inside the function to resolve the circular import, but that feels like a workaround. I've also considered refactoring the code to avoid the need for such imports, but the dependency seems essential for my current architecture. Is there a more idiomatic way to handle this circular import scenario while keeping the code clean? I'm using Django 3.2 with Python 3.9. The stack includes Python and several other technologies. How would you solve this? I'm developing on CentOS with Python. Any feedback is welcome!