-
Notifications
You must be signed in to change notification settings - Fork 366
TODO list
I was unsure of where else to put this page, but I was starting to notice a great deal of errors and logic flow problems in the book that I did not have specific commit fixes for. For instance:
-
In general, I am unsure of where to put some of my files relative to my overall project structure. Relative mentions of
# views.py
orsome_page.html
at the top of code blocks are not as helpful and should be changed to be something like# mysite/views.py
or# mysite/books/views.py
or# mysite/templates/some_page.html
or# mysite/books/templates/some_page.html
. -
Also, specifically in ch.7, it is mentioned that "community convention is to keep Form classes in a separate file called
forms.py
" instead of using views.py. So shouldn't convention be used for the rest of the example? forms.py was never used again and I was unsure of which views.py to put my new form data in. -
In the section "Tying Form Objects Into Views", we added the form logic into views.py (I thought it should have been forms.py, see #2), and we added the page template, but no mention of urls.py? "Try running this locally" is not example helpful when I get import errors trying to run it.