How to handle circular imports when using Flask blueprints in Python 3.10?
I'm prototyping a solution and I'm optimizing some code but I'm confused about I'm maintaining legacy code that I'm stuck on something that should probably be simple..... I'm currently organizing my Flask application using blueprints, but I'm running into issues with circular imports that are causing my app to unexpected result when I try to run it. Here's an example of my directory structure: ``` /myapp /__init__.py /views.py /models.py ``` In my `__init__.py`, I'm initializing the Flask app and registering the blueprint: ```python from flask import Flask from .views import main_blueprint def create_app(): app = Flask(__name__) app.register_blueprint(main_blueprint) return app ``` In my `views.py`, I'm defining the blueprint like this: ```python from flask import Blueprint from .models import SomeModel main_blueprint = Blueprint('main', __name__) @main_blueprint.route('/') def index(): return 'Hello, World!' ``` And in `models.py`, I have: ```python class SomeModel: def __init__(self): pass # Define the model ``` When I run my application, I receive an `ImportError: want to import name 'main_blueprint' from partially initialized module 'myapp.views'`. I believe this is due to the circular dependency between `views.py` and `models.py`, but I'm not sure how to resolve it without restructuring my code too much. I've tried moving the model import into the route function, but then I want to access `SomeModel` when I want to use it for database operations. How can I fix this scenario while keeping my application organized and functional? Any suggestions would be appreciated! I'm working on a web app that needs to handle this. Has anyone else encountered this? I'm working on a web app that needs to handle this. I recently upgraded to Python 3.11. How would you solve this? I recently upgraded to Python latest. Any ideas how to fix this? This is for a microservice running on Ubuntu 20.04. What's the best practice here? I'm open to any suggestions.