13π
β
I found the issue. As suspected it was something dumb.
I was missing a __init__.py
in my apps
directory.
apps/
foo/
migrations/
__init__.py
admin.py
apps.py
models.py
tests.py
urls.py
views.py
__init__.py <-- the offender
manage.py
π€Nathan
1π
A couple other places to look:
- Test filenames should start with
test
- The methods within the tests should start with
test
- If youβre using a
tests
directory be sure to add__init__.py
to the those test folders
π€jmunsch
- [Django]-Pass a lazy translation string including variable to function in Django
- [Django]-Django pre_save signal and ModelAdmin custom error message
- [Django]-Return self.user as foreignkey
0π
Just for the record: I was having the same symptom because there was an extra __init__.py
file in the projectβs directory (the same directory that contains manage.py)
Applications to test were found but then Iβd get an error that . could not be imported.
π€RobM
- [Django]-How to make a geography field unique?
- [Django]-ModuleNotFoundError: No module named 'debug_toolbar' Django 3.1
- [Django]-Django "Did you mean?" query
- [Django]-Dynamic (i.e. Runtime Configurable) Log Configuration for Django + Celery based application
Source:stackexchange.com