-
-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why is there no circular import error here? #20
Comments
I'm not sure if we are looking at the same thing, but |
I thought so too, however in my case I still get a circular import error. Here is a very simplified structure for reference: ./init.py
./api/post/init.py
./celery_app.py
The issue is Edit
|
I can't really help with the information that I have. Seems like a pretty standard circular import problem though. If your import is inside |
Seems to be the case. I temporarily resolved it by importing the celery task on the line right before where I call it but this isn't what I'd call a solution. I'm going to look into it more. I'll close this issue as it doesn't relate to this repo at this point. Thanks a lot for your answers though! |
I'm using this repo as the base for my celery implementation in a project. In my project, I am getting circular import errors, but here there aren't. Shouldn't there be?
You have
__init__.py
, which importsauth
from theviews
folder.auth
in turn has some authentication functions, one of which (register
) imports thesend_email
celery task fromemails.py
. Finally,emails.py
importscelery
from__init__.py
, therefore making it a circular import.Am I missing something here? I have a very similar setup and I am getting circular import errors.
The text was updated successfully, but these errors were encountered: