Error including app urls in project.py urls

Question

I’m at the beginning of a project with Django 2.2.1, creating the first apps and making the links between the pages. In the project’s urls.py, including the Accounts urls worked (with the include(accounts.urls), but when trying to do the same for the expenses app I’m not getting.

When running the runserver, error appears django.core.exceptions.ImproperlyConfigured: The included URLconf 'projeto.urls' does not appear to have any patterns in it. If you see valid patterns in the file then the issue is probably caused by a circular import.

I have researched and tried several things I found, but nothing is working. If anyone can help I appreciate.

py. of the project

from django.contrib import admin
from django.urls import path, include
from django.views.generic.base import TemplateView

urlpatterns = [
    path('admin/', admin.site.urls),
    path('expenses/', include('expenses.urls')),  # expenses app urls
    path('accounts/', include('accounts.urls')), #sign up
    path('accounts/', include('django.contrib.auth.urls')), #login and logout
    path('', TemplateView.as_view(template_name='home.html'), name='home'), #homepage
]

App files expenses:

py.

from django.urls import path
from . import views

urlpatterns = [
    path('create/', views.CreateExpenseView.as_view(template_name='create_expense.html'), name='create-expense'), #create new expense
]

py views.

from django.views.generic.edit import CreateView  
from .forms import ExpenseForm

#view for create a new expense
class CreateExpenseView(CreateView):
    form_class = ExpenseForm
    template_name = 'templates/create_expense.html'

py.models

from django.db import models

class Expense(models.Model):
    TYPE = (
        ('Type1', 'Type1'),
        ('Type2', 'Type2'),
        ('Type3', 'Type3'),
        ('Outros', 'Outros') #abre um campo para digitar
    )

    type = models.CharField(max_length=10, choices=TYPE, null=True, blank=True) 
    value = models.FloatField(null=True, blank=True)
    num_installments = models.IntegerField(null=True, blank=True) #parcelas
    day_installments = models.IntegerField(null=True, blank=True) #dia de pagamento de cada parcela

Answer 1

There are two urlpatterns accounts/:

urlpatterns = [
    path('admin/', admin.site.urls),
    path('expenses/', include('expenses.urls')),  # expenses app urls
    path('accounts/', include('accounts.urls')), #sign up
    path('accounts/', include('django.contrib.auth.urls')), #login and logout
    path('', TemplateView.as_view(template_name='home.html'), name='home'), #homepage
]

Translated from documentation: https://docs.djangoproject.com/en/2.2/topics/http/urls/

Naming URL patterns

To perform URL reversal, you will need to use named URL patterns, as done in the examples above. The string used for the URL name can contain all the desired characters. You are not restricted to valid Python names.

When naming URL patterns, choose names that probably won’t collide with the choice of other app names. If you call your URL default comment and another application does the same thing, the URL that finds Reverse() will depend on the pattern that is last in your project’s url pattern list.

Prefixing your URL names, perhaps derived from the application name (such as myapp-comment instead of comment), decreases the chance of collision.

You can deliberately choose the same URL name as another application if you want to replace a view. For example, a common use case is to replace Loginview. Parts of Django and most third-party applications assume that this view has a URL pattern with the login name. If you have a custom login view and provide your URL with the login name, Reverse() you will find your custom view as long as it is in urlpatterns after Django.contrib.auth.urls is included (if included).

You can also use the same name for various URL patterns if they differ in their arguments. In addition to the URL name, Reverse() corresponds to the number of arguments and the names of the keyword arguments.

So how your standards are exactly equal, no parameters, may be the cause of the problem.