CODEWITHSUNDEEP
django
HWM-Rocker
HWM-Rocker

Reputation: 617

Apps with label XYZ could not be found

today I ran into an error and have no clue how to fix it.

Error: App with label XYZ could not be found. Are you sure your INSTALLED_APPS setting is correct?

Where XYZ stands for the app-name that I am trying to reset. This error shows up every time I try to reset it (manage.py reset XYZ). Show all the sql code works.

Even manage.py validate shows no error.

I already commented out every single line of code in the models.py that I touched the last three months. (function by function, model by model) And even if there are no models left I get this error.

Here http://code.djangoproject.com/ticket/10706 I found a bugreport about this error. I also applied one the patches to allocate the error, it raises an exception so you have a trace back, but even there is no sign in what of my files the error occurred.

I don't want to paste my code right now, because it is nearly 1000 lines of code in the file I edited the most.

If someone of you had the same error please tell me were I can look for the problem. In that case I can post the important part of the source. Otherwise it would be too much at once.

Thank you for helping!!!

Upvotes: 4

Views: 4980

Answers (3)

Yellow01
Yellow01

Reputation: 11

Try to clean up all your build artifacts: build files, temporary files and so on. Also ./manage.py test XYZ will show you stack trace. Later try to run python with -m pdb option and step through the code to see where you fail and why.

Upvotes: 1

Alexandre
Alexandre

Reputation: 1285

I had a similar problem, but I only had it working after creating an empty models.py file.

I was running Django 1.3

Upvotes: 4

Amos
Amos

Reputation: 1060

You don't specify which server you're using. With Apache you'll almost certainly need a restart for things to take effect. If you're using the development one try restarting that. If this doesn't work you may need to give us some more details.

I'd also check your paths as you may have edited one file but you may be using a different one.

Plus check what's still in your database, as some of your previous versions may be interfering.

Finally as a last resort I'd try a clean install (on another django instance) and see if that goes cleanly, if it does then I'd know that I'd got a conflict, if not then the problem's in the code.

Upvotes: 0

Related Questions