Skip to content
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

python manage.py makemigrations home, catalog #387

Closed
Mcsavvy opened this issue May 30, 2021 · 5 comments
Closed

python manage.py makemigrations home, catalog #387

Mcsavvy opened this issue May 30, 2021 · 5 comments

Comments

@Mcsavvy
Copy link

Mcsavvy commented May 30, 2021

ISSUE_TEMPLATE

  • longclaw version:1.0.2
  • Django version:3.2.3
  • Python version:3.8.8

Description

I'm trying to make migrations for home and catalog but I keep getting an error.

(store) (base) ➜ alias migrations="python manage.py makemigrations"
(store) (base) ➜ migrations home catalog
Traceback (most recent call last):
File "/home/mcsavvy/projects-new/soar/store/lib/python3.8/site-packages/django/apps/config.py", line 244, in create
app_module = import_module(app_name)
File "/home/mcsavvy/anaconda3/lib/python3.8/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 973, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'core'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "manage.py", line 11, in
execute_from_command_line(sys.argv)
File "/home/mcsavvy/projects-new/soar/store/lib/python3.8/site-packages/django/core/management/init.py", line 419, in execute_from_command_line
utility.execute()
File "/home/mcsavvy/projects-new/soar/store/lib/python3.8/site-packages/django/core/management/init.py", line 395, in execute
django.setup()
File "/home/mcsavvy/projects-new/soar/store/lib/python3.8/site-packages/django/init.py", line 24, in setup
apps.populate(settings.INSTALLED_APPS)
File "/home/mcsavvy/projects-new/soar/store/lib/python3.8/site-packages/django/apps/registry.py", line 91, in populate
app_config = AppConfig.create(entry)
File "/home/mcsavvy/projects-new/soar/store/lib/python3.8/site-packages/django/apps/config.py", line 246, in create
raise ImproperlyConfigured(
django.core.exceptions.ImproperlyConfigured: Cannot import 'core'. Check that 'longclaw.core.apps.LongclawcoreConfig.name' is correct.

@chrisbarry
Copy link
Collaborator

Hey, this is the django 3.2 thing...

I haven't got time to fix now (but will in a bit)

https://www.reddit.com/r/djangolearning/comments/mlgjqn/changed_import_structure_in_django_32/

You could just downgrade django or change the app names inside longclaw, if you're comfortable doing that..

I'll do it in a bit if nobody gets there before me,

CB

@burchesoka
Copy link

Oh! can you make it in requirments.txt?

@ArthurJahn
Copy link

I'm having the same issue here.

@GH2703
Copy link

GH2703 commented Jan 27, 2022

Re: issue #443, the makemigratons problem was caused by an outdated longclaw folder installed by pip, which was weird. The updated longclaw folder was supposed to fix: AppConfig full paths (#394).

@realsifocopypaste333
Copy link

i use these modules :) its work fine :)

anyascii==0.3.1
asgiref==3.5.2
backports.zoneinfo==0.2.1
beautifulsoup4==4.8.2
certifi==2022.5.18.1
charset-normalizer==2.0.12
Django==2.2.21
django-countries==7.3.2
django-extensions==3.1.5
django-filter==2.4.0
django-ipware==2.1.0
django-modelcluster==5.3
django-permissionedforms==0.1
django-taggit==1.5.1
django-treebeard==4.5.1
djangorestframework==3.9.0
draftjs-exporter==2.1.7
et-xmlfile==1.1.0
html5lib==1.1
idna==3.3
l18n==2021.3
longclaw==1.0.2
openpyxl==3.0.10
Pillow==7.2.0
pytz==2022.1
requests==2.27.1
six==1.16.0
soupsieve==2.3.2.post1
sqlparse==0.4.2
tablib==3.2.1
telepath==0.2
typing_extensions==4.2.0
Unidecode==1.3.4
urllib3==1.26.9
wagtail==2.9
webencodings==0.5.1
Willow==1.3
xlrd==2.0.1
XlsxWriter==1.4.5
xlwt==1.3.0

@Mcsavvy Mcsavvy closed this as not planned Won't fix, can't repro, duplicate, stale Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants