Unit test for chapter 3 require specific project name

[tangowithcode]

Unit test for chapter 3 require specific project name

[maxwelld90]

Hi @BelfDev,

Thank you for getting in touch. I accept your comment, but what we are trying to say in the highlighted paragraph was that you don't have to comply with the naming convention touched upon there -- i.e. you don't have to append _project to the end of the project's name.

Given that:

• the sample command above the highlighted paragraph clearly states tango_with_django_project;
• the narrative underneath the highlighted paragraph clearly states the creation of the tango_with_django_project project/directory; and
• the use of tango_with_django_project as the project configuration directory in paragraph at the bottom of page 27,

I'm inclined to leave things as they presently are -- notwithstanding a small revision to the book's narrative to clarify that "but naming this is really entirely up to you" refers to the inclusion (or lack of) _project at the end of the project name. I'll push that tweak up for a future revision of the book, although this hasn't been highlighted as a problem in over five years.

Besides, if I were to remove the test you suggest, there are a series of tests later on that expect tango_with_django_project to be your project's name/directory anyway. So we are really gunning folk to use tango_with_django_project as their project name/directory!

Sorry if the text was confusing, and thanks for bringing it to our attention.

All the best,
David

[BelfDev]

Hi @maxwelld90,

Thanks for your response. I understand what you were trying to convey, but in the end, the test will still fail if the reader omits _project. Perhaps nobody has highlighted this in the last five years because it's just easier to copy/paste the code snippet or rename the project :)

Thanks for writing the book! I'm enjoying it, and I thought it'd be nice to give you some input.

Best,
Pedro