[Django] #35633: i found a bug in the documentation version 4.2 in Writing your first Django app, part 5

8 views
Skip to first unread message

Django

unread,
Jul 26, 2024, 10:19:22 AM7/26/24
to django-...@googlegroups.com
#35633: i found a bug in the documentation version 4.2 in Writing your first Django
app, part 5
------------------------------+-----------------------------------------
Reporter: amir20002000 | Type: Bug
Status: new | Component: Uncategorized
Version: 4.2 | Severity: Normal
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+-----------------------------------------
in the section "Create a test to expose the bug" of the
[https://docs.djangoproject.com/en/4.2/intro/tutorial05/ tutorial 5] i
write the exact code in my test.py file but when i runing the "python
manage.py test polls" command in the next section i get this error:
RuntimeError: Model class mehr_paj.polls.models.Question doesn't declare
an explicit app_label and isn't in an application in INSTALLED_APPS.

i figure out if chnage this line of test code "from .models import
Question" to this "from polls.models import Question" the problem is
solved and test code running with out the problem
--
Ticket URL: <https://code.djangoproject.com/ticket/35633>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jul 26, 2024, 3:38:19 PM7/26/24
to django-...@googlegroups.com
#35633: i found a bug in the documentation version 4.2 in Writing your first Django
app, part 5
-------------------------------+--------------------------------------
Reporter: amirreza | Owner: (none)
Type: Bug | Status: closed
Component: Uncategorized | Version: 4.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Natalia Bidart):

* resolution: => invalid
* status: new => closed

Comment:

Hello amirreza, thank you for taking the time to create this report.

I'm afraid that you may have a different local setup than the one
described in the tutorial if you are getting the shown error. Because of
that, this report seems better suited to be a support request. The best
place to get answers to your issue is using any of the user support
channels from [https://docs.djangoproject.com/en/dev/faq/help/#how-
do-i-do-x-why-doesn-t-y-work-where-can-i-go-to-get-help this link].

Since the goal of this issue tracker is to track issues about Django
itself, and your issue seems, at first, to be located in your custom code,
I'll be closing this ticket as invalid following the
[https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
tickets/#closing-tickets ticket triaging process].
--
Ticket URL: <https://code.djangoproject.com/ticket/35633#comment:1>
Reply all
Reply to author
Forward
0 new messages