Django Structure

Hi, I am new to Django, I read your Tutorial, very interesting and after reading also the tips given, after installation I created the Project.
Below is the structure of the project
I make a summary for clarity. The working folder is called PalestraGes which will have inside it a folder with the same name for the settings of the whole project and the Project folder called Pale


The structure is complex but later I will have to make a complex project and I have read that it is good to put the files in different folders
The file I renamed it to because it is incopatible with the views folder I created
Based on this structure I tried with a first file.
In models I inserted the fields of the Regioni table.
In urls (of Pale) I inserted the path

# ... importo TABELLE
from Pale/views/Pale/Tabelle/RegioniViews import Regioni
path('RegioniLista/', Regioni, name='RegioniLista'),

In views/Pale/Tabelle/

from Pale.models import Regioni
from Pale.forms.Pale.Tabelle import RegioniForm
class RegioniListaView(View):
    def regioni_lista(self, request):
        Regio = Regioni.objects.all()
         return render(request, 'RegioniLista.html', {'Regioni': Regio})

In templates/Pale/Tabelle/RegioniLista.html

{% extends 'base.html' %}
{% block content %}
Pagina delle Regioni
{% endblock %}

From the RegionsList site, I get the error back.

AttributeError at /RegionsList/.
'Regions' object has no attribute 'get'

And I don’t know in which file I got the code wrong.

Sorry if I was long but I preferred to give a complete picture

This error means that the region object you are sending doesn’t have the key get
To solve this error, can you check your views and template.
How are you using region object being sent in view

Side note: When you’re posting code or templates or preformatted text here, surround the text between lines of three backtick - ` characters. This means you’ll have a line of ```, then your code (or template, etc), then another line of ```.

You shouldn’t just “read” the tutorial. For you to get the most value from it, you need to work your way through it. This includes typing all the code and other exercises.

I’m not sure what you may have read - or where - but I always recommend that you stick with the Django defaults and standards until you get to the point where you need a different structure.

I’ve been using the defaults for about 10 years now, and have never run into a situation where we’ve needed to use anything else.

Also, you may want to review the docs at Class-based views | Django documentation | Django

With your help, I have a clearer idea and have solved
Thank you