Create a Template

Im really enjoying this great module thanks. When i added the code below i got an error. However, i actually didnt need to add the following as mine worked fine without it. Thanks

TEMPLATES = [ { “DIRS”: [os.path.join(BASE_DIR, “projects/templates”),] } ]

@seangoodman37 there’s been an update in how Django handles paths since we recorded this tutorial.

There’s an in-depth explanation in a comment a little further up, hope that helps.

Hey, I was able to get everything to work but I got an additional warning from pylint that I was curious about. Warning (severity 8 whatever that means):

"message": "Module 'projects.views' has no 'project_list' member",

However everything is functioning correctly and I do have:

from django.http import HttpResponse
from django.shortcuts import render

def project_list(request):
    return render(request, 'projects/index.html')

in my project.views. Curious what this is and what effect it could have in the future.

Hi. When I tried registering the templates folder in the settings.py page, I was getting os not found error. Then I checked the settings page completley. In my page it didn’t have the import os command predefined and the Base_DIR line was different. Can you please help (Plus I am using VScode as editor)

@simma99 like mentioned earlier, there’s been an update to Django that changed OS operations to using pathlib instead of os.

You can read more in an in-depth comment further up.

@Martin Breuss thanks for the help. It worked without defining anything in the DIR and keeping APP DIR True.

BASE_DIR = Path(__file__).resolve().parent.parent

'DIRS': [Path.join(BASE_DIR, 'projects/templates')]

This is not working, do I need something else in my base directory?

Nevermind, I did not see the explantion above. Thanks.

I am using VS Code, Django version 5. When I left the project and returned, I activate my environment and then run “python manage.py startapp projects”. I got the error “CommandError: ‘projects’ conflicts with the name of an existing Python module and cannot be used as an app name. Please try another name.”

I searched for the cause of this and the solution I found was to change the name of my project. I did to “myprojects”. This worked for a few days. I return to the project today and am receiving the same error, now for “myprojects”.

I know I should not have to change the name of the project again. There is something else. Should I not have run startapp again? What are the steps I should take when I leave this project, work on something else and then return? Thank you.

@marksemmelbeck every time that you run startapp, Django tries to create a new app. Because you’ve already created an app with the same name (first projects, then myprojects), the command fails with the message that you mentioned. Python calls your app a “module” in the error message, which might be confusing. It is a module, so the message is correct, but if you think of it only from a Django perspective, then it might be more straightforward if the message read something like this instead:

CommandError: ‘projects’ conflicts with the name of an existing Django app in your project. Please try another name.

All that running startapp does is to create the app’s folder structure. You already got that after running it the first time, so you don’t need to run that command again unless you want to create a different app.

The steps you need to take when returning to the project after you’ve worked on something else are:

• Activate your virtual environment (if you’re using one)
• Run python manage.py runserver, which starts the development server

That’s all : )